On 21/09/2011, at 5:52 PM, davide.cavestro wrote: > This is how I adapted your snippet to be able to exclude project dependencies > artifacts. > > > Now the problem is that it copies the right contents, but the files have > unusable names, (i.e. /e6def06602b51b1d9be51f6c3fcdf163ecd01644/ instead of > /jsp_api.jar/). It is the name of the actual files into gradle cache > filestore. I suppose when the symlink is resolved the original artifact name > get lost.
This is an issue in 1.0-milestone-4: http://issues.gradle.org/browse/GRADLE-1727. This has been fixed, to be included in the upcoming Gradle 1.0-milestone-5 release. The issue wasn't present in 1.0-milestone-3, so you might down-grade to milestone-3 until milestone-5 is released. > I guess I could use temporary files, but it somewhat cumbersome and moreover > I'd like to avoid unnecessary io. Any idea on how to exclude project deps > and still retain the resolved artifact original name? > Cheers > Davide > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/How-to-export-actual-deps-artifacts-to-a-flat-dir-repository-tp4821778p4825477.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
