If you're getting the regular spring (classes) jar with just "-sources" appended to the name, I would suspect an Artifactory configuration issue. You could check this by accessing the artifactory urls directly and checkin the result.
But once the incorrect jars are in the Gradle cache this way, the only way (currently) to fix this is to remove your ./gradle/caches/artifacts-4 directory. We're currently working on a way to force gradle to verify the cached jars against the server, but that won't be available until the next release. cheers Daz On 10 January 2012 07:40, bedminster <[email protected]> wrote: > Hello, > > I have populated an Artifactory Ivy repository with all my project’s third > party dependencies, source jars, & javadocs. I am on Gradle version --> > gradle-1.0-milestone-6. > > Using my Gradle build script I can build successfully (pulling all the > configured dependencies from Artifactory) and publish the project > artifact(s) to Artifactory (using the Gradle Artifactory Plugin OR via > Jenkins using the Artifactory plugin). > > However I have noticed that when building my project, only the third party > dependency jars are carried over from Artifactory into my local file system > Gradle cache, but none of the associated source jar and javadoc zip files. > These are pretty standard 3rd party dependency files (spring framework, > slf4j, commons.*, etc). Not sure if it is an Ivy, Gradle, or an > Artifactory issue(?). For the purposes of my Gradle Eclipse Plugin > integration having the javadocs and source files at my disposal is key. > > Within my Gradle script's eclipse configuration block I have explicitly set > the downloadSources & downloadJavadoc values to true > > eclipse { > //default settings for dependencies sources/javadoc download: > downloadSources = true > downloadJavadoc = true > } > > Here is an example spring framework entry taken from my generated > .classpath > file. > > Yes, I have a sourcepath entry, but it isn't the actual > org.springframework.beans source jar. It's merely the original jar file > with an appended "-sources.jar" file. > > <classpathentry > > sourcepath="C:/Users/bedminster/.gradle/caches/artifacts-4/org.springframework/org.springframework.beans/5b254350c22ca2a465f43872accbd613/sources/<b>org.springframework.beans-3.0.5.RELEASE-sources.jar*" > kind="lib" > > path="C:/Users/bedminster/.gradle/caches/artifacts-4/org.springframework/org.springframework.beans/5b254350c22ca2a465f43872accbd613/jars/org.springframework.beans-3.0.5.RELEASE.jar" > exported="true"/> > > Again I am not sure what are the underlying issues here. Could it possibly > be my custom Artifactory Ivy repository layout? Or could it be that the > 3rd > party module's Ivy.xml publications need to be configured or set-up a > certain way? > > I certainly appreciate in advance any assistance that can be provided. > > -Brett > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Downloading-3rd-party-source-and-javadocs-from-Artifactory-Ivy-repo-tp5134221p5134221.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 > > > -- Darrell (Daz) DeBoer Principal Engineer, Gradleware http://www.gradleware.com
