On 05/08/2011, at 5:03 PM, Thomas Fuchs wrote: > Hi Luke, > > we are also accessing the cache directly, because we clone the cache to our > own > local validated Jar-Repository. The old structure of the cache was perfectly > fine for this. > Everything worked out of the box with <5 lines of gradle code. > Now the simple copy task will become more complicated to remove the hash code. > > So I'm very interested in possible alternative ways you could think of!
There's unfortunately not a simple way with m4. Please raise an issue to ensure it's something that becomes supported. The solution will be some kind of task to take one or more configurations and lay the dependencies out somewhere, avoiding direct referencing of the cache. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com
