[GRADLE-1613] Classpath entries generated by the Eclipse plugin are always exported="true" Created: 14/Jun/11 Updated: 04/Jan/13 Resolved: 05/Jul/11
|Affects Version/s:||1.0-milestone-3, 1.0-milestone-4|
|Reporter:||David Gileadi||Assignee:||Szczepan Faber|
The Eclipse plugin currently always generates classpath entries with the "exported" attribute set to "true". In multi-project builds this means that depending Eclipse projects see all dependencies of dependent Eclipse projects, even dependencies which Gradle would typically not export.
This is an issue for testCompile and testRuntime dependencies, and it's also an issue when creating a "provided" configuration as described in the EclipseClasspath documentation. "provided" dependencies should never be exported, and can cause conflicts in depending projects.
This is an issue with a rather large and complicated build I'm currently involved with using the gradle-m2metadata plugin.
|Comment by David Gileadi [ 14/Jun/11 ]|
Created a patch that fixes this bug at https://github.com/gradle/gradle/pull/38
|Comment by Szczepan Faber [ 05/Jul/11 ]|
Once milestone-4 is released the example will be shown here: http://gradle.org/current/docs/dsl/org.gradle.plugins.ide.eclipse.model.EclipseClasspath.html