Cannot swicth worksapce in Eclipse Kepler SR2 when using lombok #701

Closed
lombokissues opened this Issue Jul 14, 2015 · 6 comments

Projects

None yet

2 participants

@lombokissues
Collaborator

Migrated from Google Code (issue 666)

@lombokissues
Collaborator

👤 jcdesrochers   🕗 Apr 08, 2014 at 12:30 UTC

What steps will reproduce the problem?

  1. Install Kepler SR2 (on OS X) and install lombok
  2. Open your ecplise workspace
  3. Switch your eclipse workspace

What is the expected output? What do you see instead?
Expected to see my new workspace, but instead I got this error (see attached) along with the error message:

An internal error occurred during: "Initializing Java Tooling".
Duplicate field name&signature in class file org/eclipse/jdt/internal/compiler/ast/ASTNode

When I do the same WITHOUT lombok installed in eclipse, everything works just fine.

What version of the product are you using? On what operating system?
Running OS X 10.9.2, Java 7.0.51 and latest lombok. Even tried the nightly build (version: 1.12.7 2014-04-01 23:21 UTC), but gave the same result.

Please provide any additional information below.
The issue is also documented here: http://stackoverflow.com/questions/21931107/eclipse-wont-switch-workspace

@lombokissues
Collaborator

👤 jcdesrochers   🕗 Apr 08, 2014 at 12:30 UTC

@lombokissues
Collaborator

👤 simonwielens   🕗 Apr 17, 2014 at 11:36 UTC

Also seeing this issue in Kepler in Windows 7

@lombokissues
Collaborator

👤 reinierz   🕗 May 12, 2014 at 13:17 UTC

Potential fix just released on edge:

https://projectlombok.org/download-edge.html

@lombokissues
Collaborator

👤 reinierz   🕗 May 12, 2014 at 13:25 UTC

This fix has been reported to be working. Thanks for testing it go to ron of freenode's ﹟﹟java!

This fix will be rolled out in the next release, which will probably be 1.14. (version bump due to configuration mechanism, a new major feature). Until then, if you can't wait, the edge release has the fix.

@lombokissues
Collaborator

End of migration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment