Open f425 opened 2 months ago
There seem to be several issues related (or unrelated) to the Javadoc comments of the @Builder
class in the latest Lombok 1.18.34. (issue 1, issue 2)
The version of Lombok bundled in this extension is from https://projectlombok.org/lombok-edge.jar
, which currently delivers the same binary as Lombok 1.18.34, thereby affecting this extension.
Temporary solutions I discovered:
lombok/lombok-1.18.33.jar
bundled in v1.32.0
.vsix
file yourself@heguro
Lombok
version is 1.18.12
in my demo project.
Before this extension v1.33.0, it was working fine.
Is it fixed in the latest version
Which version are you referring? I have the Language Support for Java(TM) by Red Hat v1.35.202408 and the bug is still there.
when this will be fixed
Lombok has merged a fix as of a few days ago (see https://github.com/projectlombok/lombok/pull/3726), but they have not done a release yet. So I assume that will have to happen first so that an updated version of Lombok can be bundled with the extension.
https://github.com/redhat-developer/vscode-java/issues/3561#issuecomment-2442023671 woke me up. Could someone try the vscode-java pre-release and see if the problem is resolved ? According to https://github.com/redhat-developer/vscode-java/blob/0f89a67eaf7a0189e3da172a02e277d128a96cc7/gulpfile.js#L132 (the 1.18.33 label we give is wrong, but it's definitely the latest), we're using the latest lombok edge release, which is from 2024-10-18. That definitely should have the fix. If it doesn't work then the problem was never fixed by the PR.
demo
env
C:\Program Files\Java\jdk1.8.0_202
setting.json
about java and gradle:C:\\Program Files\\Java\\jdk1.8.0_202
(Oracle jdk8 for code project)C:\\Program Files\\Eclipse Adoptium\\jdk-17.0.12+7
(for vscode language server)problem
Extension: Language Support for Java(TM) by Red Hat
tov1.33.0
. Got error:Extension: Language Support for Java(TM) by Red Hat
tov1.32.0
. It's OK.Extension: Language Support for Java(TM) by Red Hat
withv1.33.0
.Data1.java
toData2.java
and delete comments.Data2.builder().build()
is ok