microsoft / microsoft/vscode-java-pack

Opening project as workspace causes language server to ignore java.jdt.ls.vmargs

Offen
#988 5 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@testforstephen arbeitet bereits daran.

Seit 05.5.2022.

ai-triaged bug lombok settings
Vorherrschende Sprache
TypeScript
Sterne
352
Forks
166
Ø Merge
17 Std. 47 Min.
Gemergte PRs (30 T.)
32

Beschreibung

I can't reproduce this on all workspaces, but for a strange reason some projects have issues with Lombok auto-generated methods when using the Java Extension Pack where the language server fails to recognize Lombok auto-generated methods.

The root cause appears to be that the java.jdt.ls.vmargs global setting is ignored, and the language server JVM is launched without the -javaagent:/path/to/lombok.jar that the VS Code Lombok extension injects. When opening the same affected project as a folder instead of as a workspace, the vmargs are injected correctly.

Environment:

  • VS Code Version: v1.66.2
  • Extension Version: v0.22.4
  • JDK Type & Version: Termurin 18
  • OS Type & Version: Mac

Step to Reproduce:

  1. Open project as workspace
  2. Enable/install Java Extension Pack and Lombok extensions
  3. Write a POJO making use of @Getter and @Setter Lombok annotations
  4. Try to call the getters of said POJO from another class

Expected Behavior:
Code intellisense/autocomplete shows Lombok-generated getters and setters, and code written calling the getters and setters has no errors.

Actual Behavior:
VS Code claims the getters and setters are undefined methods, and will not build or compile the project. Maven can compile the code with a mvn clean compile normally.

Related Issues:
Possibly related to https://github.com/redhat-developer/vscode-java/issues/1802

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.