-
-
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] lombok.eclipse.handlers.HandleBuilder failed - Java 22, Eclipse 2024-03 #3648
Comments
For me, it is VSCode 1.87.2, vscode-java 1.29.0, JDK 21 (Temurin-21.0.2+13) and Lombok 1.18.32.
There is a reported issue at vscode-java, too. |
Similar issue:
TEMP SOLUTION |
Does #3633 fix this issue? |
@yuzawa-san Yes, it really seems to fix the issue. Tested it with eclipse.jdt.ls |
Bump to release a new version with this fix. |
@yuzawa-san Sorry for late reply. It looks like the isue is fixed with #3633. |
I think this warrants an emergency stable release. I'll discuss it with @rspilker – Until then, current edge release includes this patch. |
Replacing RedHat Java extension Lombok jar with the Lombok snapshot release jar (v1.18.33), fixed the issue for me. |
Yes this fixed for me too but it's really cumbersome, couldn't be possible to have a new version with this fix? |
@rzwitserloot the issue still very much exists in the latest VSCode v1.90.2 with the latest RedHat Java extension v1.31.0. Please re-open. |
The only possibility to make Lombok work in VSC is to install the latest Language Support for Java(TM) by Red Hat that in the moment I am writing is: v1.31.0 and change the installed Lombok plugin with the SNAPSHOT one.
The SNAPSHOT could be downloaded from here: Lombok Cutting Edge build Thanks, |
No need to do that, just install pre-release version of RedHat Language Support for Java for VSCode |
Describe the bug
@Builder
annotation failes in combination with@Singular
annotation. Stack trace:To Reproduce
Install Eclipse 2024-03 with Java 22 support and Lombok 1.18.32. Add class:
Version info:
The text was updated successfully, but these errors were encountered: