[GRADLE-3393] Duplicate source folders created when using eclipse.classpath.whenMerged Created: 08/Feb/16  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Stefan Oehme (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

When changing the source folders inside the `eclipse.classpath.whenMerged` hook, the classpath will contain duplicate source folder entries when `gradle eclipse` is run twice.

See https://discuss.gradle.org/t/eclipse-plugin-tweaking-sourcefolders-output-creates-duplicates/14150

The merged classpath contains both the source folders from the previous file (which have modifcations to them) and the source folders from the Gradle model (which have no modifications). Since they are not equal, both end up in the classpath file.

The current workaround is to explicitly de-duplicate them in the `whenMerged` hook, as shown in the linked forum post.

A possible solution would be to mark all entries created by Gradle with a classpath attribute and then filter those out before merging the classpath.

 Comments   
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:47:37 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.