[GRADLE-1503] Eclipse classpath task doesn't respect transitive setting (regression) Created: 30/Apr/11 Updated: 10/Feb/17 Resolved: 10/Feb/17
When generating an Eclipse classpath, Gradle will include transitive dependencies of a dependency in the classpath file, even when transitive is set to false on the dependency. This happens in the following case. Project 1 has dependency A and transitive is true. Project 2 has dependency A also, but transitive is set to false. Project 2 also has a dependency on Project 1. The Project 2 classpath will include all transitive dependencies of the dependency even though transitive was set to false.
This did not happen in Gradle 0.9.2 - the transitive dependencies were not included in Project 2's classpath file.
Attached is a sample that demonstrates the problem - run "eclipseClasspath" under Gradle 0.9.2 and then 1.0-milestone-3. Project 2's classpath will have the included transitive dependencies when run under 1.0-milestone-3, but not when run under 0.9.2.
I believe 0.9.2 is the correct behavior.
|Comment by Benjamin Muschko [ 15/Nov/16 ]|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.
We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.
Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Benjamin Muschko [ 10/Feb/17 ]|
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.