I have built a custom repository layout (with dependency metadata not in the maven .pom or gradle module metadata format.) I already have systems to do this artifact tree fetching, however id like to add gradle support. Anyone have suggestions on how to most elegantly define this type of behavior in Gradle? I have built many gradle plugins before but my depth of knowledge into how specific mechanisms of dependency resolution work in Gradle is not good, I could imagine a custom Configuration (and overriding

Set<File> resolve()

, but this seems clunky if not downright dangerous) or possibly a custom

ArtifactRepository

implementation?