We are looking to hook into a vendor's proprietary repository for our 
Gradle dependencies.  The way their repository works doesn't mesh well 
with Ivy, so a full-fledged implementation of DependencyResolver would be 
an inefficient hack-job.

What is the best way to hook into Gradle's dependency system without a 
DependencyResolver?  The only option I see so far is to implement a 
SelfResolvingDependency and providing a method to the build script (maybe 
injected into the DependencyHandler) to declare them.  One weakness with 
that is that the dependencies wouldn't be cached in Gradle's cache.  Is 
there any way to get into the dependency cache without using the 
repository mechanism?

Andy Oberstar

Reply via email to