-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Eclipse 4.23 refactor/rename from within Java Source Editor throws java.lang.VerifyError: Bad type on operand stack #3134
Comments
|
Relevant source files:
|
In that code, the result is in fact assigned to an |
D'oh, @Rawi01 already figured it out. |
I self-assigned it to let you know that I'm working on it 😄 The |
Impressive response time. Fix works for me. Thank you so much! |
hope all can be solved soon, I find this same issue today when updated accidentally eclipse |
JDK 18 (release in 6 days) also requires some changes so I guess there might be a new release version soon. I uploaded a pre-built version if you need the fix right now. |
Thx for the quick fix. The pre-built works for me. |
Can we get an updated snapshot version? As people update to Eclipse 2022-03 they come over to the eclipse side with puzzled bug reports, and there are surely more that don't report it but blame it on Eclipse ... |
The current snapshot version is updated, no? |
I updated the issue description, in case people land on this issue page, coming from any context, so they quickly get directed to the fixed snapshot download. |
This guy says it isn't: https://bugs.eclipse.org/bugs/show_bug.cgi?id=579339 (I couldn't check yet as I'm still on a working milestone build of Eclipse) |
I updated the link to the fixed version in the description (https://github.com/projectlombok/lombok/files/8274291/lombok.zip). |
thanks! |
Question: might this issue be related, too? https://bugs.eclipse.org/bugs/show_bug.cgi?id=579341 |
I was so perturbed as to why my new Eclipse won't rename anything anymore! Thanks for the quick fix, Lombok is the best! |
It seems the issue is still not completely fixed. Try to rename the file using Crtl+Shift+R by clicking the on the file in the package explorer. The window and different options in the toolbar menu starts flickering. |
@shankarwww If I press Ctrl+Shift+R it opens a seperate rename dialog and I cannot see any flickering. Can you share some more details? |
I had a "flickering issue" with something totally unrelated to lombok, but what was the same was that the keyboard shortcut was ambiguous - I had two commands associated to the same key binding.
|
@shankarwww Hopefully this will help resolve it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=579483 |
after i tested with 1.18.24 and sts Version: 4.14.0.RELEASE |
@user20161119 In eclipse menu: |
|
@user20161119 That is not the error log. The error log contains, well, errors, and generally includes a stack trace. There's nothing we can do (short of just downloading STS, clicking around, and praying we hit the same issue. We're not going to do that) without this information, and the issue will remain closed until it is provided. |
Given a fresh Eclipse install from upcoming 4.23.0 Release (Candidate Build: 4.23RC2a), it appears that when Lombok is installed as java agent in eclipse.ini
the Eclipse refactor feature no longer works from within the Source Editor window.
NOTICE
To Reproduce
Given plain Java (no Lombok) ...
when trying to refactor/rename the
message
variable (e.g. select the text and use the context menu), Eclipse throws ajava.lang.VerifyError.
Version info:
Additional context
Eclipse also has a Code Outline view, from where one can initiate a refactor/rename e.g. on class fields. It appears that with that there are no issues.
The text was updated successfully, but these errors were encountered: