I have a project with a mix of external dependencies. Most libs have sources
but some custom jars I need don't have associated sources. They are just
plain jars on the filesystem. I include them like so:
repositories {
flatDir name: 'localRepository', dirs: "$projectDir/lib"
.... mavenLocal() artifactory mavenCentral() etc...
}
In 0.9.2, "gradle eclipse" properly brings down source jars for the ones it
can find, and quietly continues when it can't find sources for my local
libs.
However in 1.0-milestone-3, it complains about the sources it can't find and
the build actually fails with unresolved dependencies. :(
Of course there's eclipseClasspath.downloadSources = false but that turns
off ALL downloading of sources. I'd like to be able to have the 0.9.2 way
of handling sources it can't find by just continuing without failing the
build. It's ok if it prints out a message saying it can't find some sources,
but I think it's harsh for the build to fail just cause it can't find some
source jars.
Is there an interim solution? (I'll go back to 0.9.2 for now...)
--
View this message in context:
http://gradle.1045684.n5.nabble.com/1-0-milestone-3-gradle-eclipseClasspath-fails-build-when-local-libraries-don-t-have-sources-tp4462119p4462119.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
