On 01/08/2011, at 12:26 AM, Jeff Brown wrote: > In Grails we have some code in our build that copies jar files from > the Gradle cache to another location (we do have a good reason for > this but that isn't relevant to my question). In 1.0-milestone-3 we > look for the artifacts at a location like this: > > /Users/jeff/.gradle/cache/org.codehaus.groovy/groovy-all/jars/groovy-all-1.8.0.jar > > In 1.0-milestone-4 they are located at a location like this: > > /Users/jeff/.gradle//caches/artifacts/org.codehaus.groovy/groovy/30ff99c0bcf5520fb6f0e1c2fb71006d/jars/groovy-1.8.0.jar > > The cache directory is now caches/artifacts, which is not a problem. > I am curious about the hash part of the directory structure. Is that > intentional?
Yes it is. The hash identifies the repository that the artifact came from. What's your reason for accessing the cache directly? Maybe we can find an alternative way. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
