Thanks Daz, The issues were one part Artifactory configuration (repository layout pattern) and second part the naming convention applied to the source distributions as pulled from the Spring ERB site.
I went ahead and removed the /gradle/caches/artifacts-4 directory, re-ran my gradle build script, specifying the eclipse task, and all is well. My .classpath file pulls in the the sources and javadoc when applicable. However, I have yet another question as it relates to the eclipse plugin and the gradle cache. I am tinkering with the option to generate a .classpath with relative links as described in this Gradle forum post, http://forums.gradle.org/gradle/topics/removing_absolute_paths_from_eclipse_classpath_file. A generated .classpath file could then be added to source control without it containing any "local" absolute path reference(s). But how would this work with the new gradle dependency caches, where unique checksums are appended in the following manner? C:\Users\bedminster\.gradle\caches\artifacts-4\org.springframework\spring-aop\08da4c2452bf16f149cad366f4174ede\ Any thoughts? Thanks again! -Brett -- View this message in context: http://gradle.1045684.n5.nabble.com/Downloading-3rd-party-source-and-javadocs-from-Artifactory-Ivy-repo-tp5134221p5155720.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
