[GRADLE-1835] Eclipse plugin doesn't update .classpath properly if build has dependency on project with different JAR version Created: 14/Oct/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: Bug
Reporter: Jeff Sussna Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Given the following dependency list, if the depended-upon project has its own dependency on a different version of junit, then running 'gradle eclipse' on the dependent project will not add the junit reference to .classpath.If I remove the 'compile project' reference, or change the junit version to match the one used by depended-upon-project, then the junit ref will be added to .classpath.


{ groovy group: 'org.codehaus.groovy', name: 'groovy-all', version: '1.7.10' compile project(':depended-upon-project') compile group: 'junit', name: 'junit', version: '4.5' }

Comment by Jeff Sussna [ 14/Oct/11 ]

Sorry, this should be a minor bug, not a major. Don't seem to be able to change it after creation.

Comment by Stefan Sieber [ 09/Jan/12 ]

Are you sure it's not added to the classpath?
Isn't it just a problem of the ordering, i.e. depended-upon-project (and therefore its JUnit - jar) appears before JUnit 4.5?
I'm currently experiencing a similar issue where the problem is caused by the ordering.

Comment by Jeff Sussna [ 20/Jan/12 ]

Could be. I haven't worked on the offending project in quite a while, so I'd have to take some time to go back and look.

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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

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.

Generated at Wed Jun 30 12:05:38 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.