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

Aperta
#988 5 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@testforstephen ci sta già lavorando.

Dal 5/5/2022.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

ai-triaged bug lombok settings

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

Lingua principale
TypeScript
Stelle
352
Fork
166
Merge medio
17h 47m
PR unite (30g)
32

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/vscode-java-pack

Tutte le issue di microsoft/vscode-java-pack

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.