Skip to content
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

(Lombok) annotations with arguments show an error in releases after 1.25.1 #3454

Closed
DempseyRoller opened this issue Jan 9, 2024 · 3 comments · Fixed by #3456
Closed

(Lombok) annotations with arguments show an error in releases after 1.25.1 #3454

DempseyRoller opened this issue Jan 9, 2024 · 3 comments · Fixed by #3456

Comments

@DempseyRoller
Copy link

[(Lombok) annotations with arguments show an error.]

Type: Bug

Environment
  • Operating System: Windows 11 / WSL: debian
  • JDK version: OpenJDK 17
  • Visual Studio Code version: 1.85.1
  • Java extension version: 1.25.1+
Steps To Reproduce
  1. Install latest pre-release
  2. Use a lombok annotation with a argument such as @EqualsAndHashCode(callSuper = true)
Current Result

Annotations with arguments mess up the annotation reading of VSCode resulting lot's of erros in the editor.

Expected Result

Annotations are read as before.

Additional Informations

The bug appeared somewhere in the first half of last December. I fixed it today by installing the current stable 1.25.1 version, instead of a prerelease.

@rgrunber
Copy link
Member

rgrunber commented Jan 9, 2024

We're aware of this issue in pre-releases. This is a duplicate of eclipse-jdtls/eclipse.jdt.ls#2985 . We're aware of the issue, which is partly why we avoided releasing for so long. We filed at projectlombok/lombok#3564 , and are trying to get a fix into projectlombok/lombok#3565 but it's taking longer than expected.

The problem is this is basically holding us up from doing a release of other nice improvements.

@rgrunber
Copy link
Member

We have a solution (to avoiding the regression) that should be an acceptable workaround. Going to try to see if we can implement it for this release!

@Tomnivore
Copy link

Thank you. And sorry for the inconvinience. I tried to do a quick search if there were any recent annotation issues, but didn't catch my eye. Cool that there's a work around now tho!

rgrunber added a commit to rgrunber/vscode-java that referenced this issue Jan 10, 2024
rgrunber added a commit to rgrunber/vscode-java that referenced this issue Jan 10, 2024
@rgrunber rgrunber added this to the Early January 2024 milestone Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants