[GRADLE-2294] eclipse and idea plugin do not fully respect the dependency order Created: 12/May/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 6


I didn't find and explicit ticket for that, however there are related tickets out there that should be merged / closed when we fix this ticket.

Eclipse and Idea plugin (and consequently the tooling api) provide a list of classpath libraries that do not fully respect the order they are declared in the build (and consequently, the order that is used to run tests, etc.). For example:

dependencies {
  compile files('foo.jar')
  compile project(":someProj")
  compile "junit:junit:4.10"
  compile files('bar.jar')
  compile project(":otherProj")
  compile "org.mockito:mockito-core:1.9.0"

Try to generate classpath for IDEA or Eclipse - the order of dependencies is different than expected.

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:18:02 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.