[GRADLE-1302] Eclipse plugin should generate classpath for all source sets. Created: 12/Jan/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Paul Cager Assignee: Unassigned
Resolution: Won't Fix Votes: 1


If you use an integration test setup along the lines of the "withIntegrationTests" sample, then the eclipse plugin does not generate entries in .classpath for dependencies in the integrationTest configuration.

A work around is to use the 'plusConfigurations' property of the EclipseClasspath task, but the task should really process all source sets.

Please see http://gradle.1045684.n5.nabble.com/integrationTest-and-eclipse-plugin-td3334702.html for more information.

Comment by Peter Niederwieser [ 25/Jan/11 ]

I'm not sure how to go about this. Including all configurations by default would be easy but probably isn't desirable. Including the compile/runtime class path of all source sets is problematic because the class paths are modeled as a collection of files rather than a collection of dependencies. Hence it is difficult to tell apart project and library dependencies (which have different representations in the .classpath file).

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 11:52:06 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.