[GRADLE-1315] Eclipse task duplicates entries in existing .classpath file Created: 18/Jan/11  Updated: 03/Feb/17  Resolved: 03/Feb/17

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

Type: Bug
Reporter: Peter Niederwieser Assignee: Unassigned
Resolution: Won't Fix Votes: 7


Created an Eclipse project by hand, then ran gradle eclipse. Resulting .classpath file looks like this:

  <classpathentry kind="src" path="src"/>
  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6"/>
  <classpathentry kind="con" path="org.eclipse.jdt.junit.JUNIT_CONTAINER/4"/>
  <classpathentry kind="output" path="bin"/>
  <classpathentry kind="output" path="build/classes/main"/>
  <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER" exported="true"/>

The file now contains duplicate entries for output folder and JRE_CONTAINER which probably don't make sense.

Comment by Zbigniew Sokolowski [ 14/Nov/12 ]

when is supposed date to repair it? this bug is just annoying, thanks

Comment by Dorothy Valiga [ 03/Mar/16 ]

I ran into this issue today (March 3, 2016) using Gradle 2.11 and Eclipse Mars.2

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 Dorothy Valiga [ 15/Nov/16 ]

Confirmed that this is complete. Please keep this issue alive.

Comment by Benjamin Muschko [ 26/Jan/17 ]

@Dorothy I don't understand your comment. Did you mean to say that it is fixed or not?

Comment by Dorothy Valiga [ 27/Jan/17 ]

Meant to confirm that I still advocate for the JIRA issue. and that the "above is complete info" per the instructions to Please keep the issue alive and open it on GitHub.

Comment by Benjamin Muschko [ 02/Feb/17 ]

@Dorothy I suggest running gradle cleanEclipse eclipse to ensure that the project files are created independent of what already existed. The IDE plugins do not check what already exists and also does not clean up duplicates.

Comment by Benjamin Muschko [ 03/Feb/17 ]

From my perspective you can just run the cleanEclipse task beforehand and ensure that existing entries are not messed up. Please open an issue on GitHub if you think that there's a problem with the approach. I'd also suggest you explore Buildship. It's likely that you can just use that as it has gotten so much better than years ago.

Generated at Wed Jun 30 11:52:26 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.