Hi there, additional to the problems bryan reported. I have the problem that my classpath contains duplicate entries. It seems that libs/containers/src paths are not merged correctly if they are not marked as exported in the origin classpath file. seems like a bug.
regards, René Am Fr, 6.08.2010, 09:49, schrieb Hans Dockter: > Thanks for reporting this. I will try to fix this for 0.9-final. > > > - Hans > > > -- > Hans Dockter > Founder, Gradle > http://www.gradle.org, http://twitter.com/gradleorg > CEO, Gradle Inc. - Gradle Training, Support, Consulting > http://www.gradle.biz > > > On Thu, Aug 5, 2010 at 2:49 AM, bryan <[email protected]> wrote: > > >> >> I thought I'd come up with a more complete example to illustrate the >> issue. Here is a build script: >> >> >> >> apply plugin: "java" apply plugin: "eclipse" >> >> repositories { mavenCentral() } >> >> >> configurations { compile { exclude group:"commons-logging" } >> } >> >> >> dependencies { compile "org.springframework:spring-core:3.0.3.RELEASE" } >> >> >> >> When you run "gradle eclipseCp" with 0.9preview3, commons-logging is >> not added to the .classpath file, as expected. When you run "gradle >> eclipseClasspath" with 0.9rc1, commons-logging IS added to the >> .classpath >> file. >> >> -- >> View this message in context: >> http://gradle.1045684.n5.nabble.com/Eclipse-classpath-in-0-9-rc1-ignores >> -excludes-tp2264807p2264845.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 >> >> >> >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
