redhat-developer / redhat-developer/vscode-java
Intellisense only works when language server is in LightWeight mode.
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 2.3k
- Forks
- 546
- Ø Merge
- 20 Std. 1 Min.
- Gemergte PRs (30 T.)
- 11
Beschreibung
Java Intellisense only works when the language server is in LightWeight mode. It breaks immediately every time I swap to Standard mode. (For me, this has been through use of Run/Debug.)
Possibly relevant excerpt from the language server's log:
!ENTRY org.eclipse.jdt.ls.core 4 0 2021-02-16 10:21:35.929
!MESSAGE file:///Users/jahorton/AlphaTiles/AlphaTilesEditor/src/main/java/org/alphatilesapps/alphatiles/data/Word.java does not resolve to a ICompilationUnit
It's definitely part of the project and is compiled as such
Environment
- Operating System: macOS 10.15.7
- JDK version: OpenJDK 13.0.1
- Visual Studio Code version: 1.53.2
- Java extension version: 0.75.0


The latter one (Visual Studio IntelliCode) is part of the Java Extension Pack, which also contains this extension, so I would expect compatibility.
Steps To Reproduce
Just to be explicit, this works for me from a clean reset, for which I do the following:
- Hit F1
- Java: Clean Java Language Server Workspace (then confirm yes to restart & delete)
After a reset, as long as it does reset to LightWeight mode, Intellisense works normally. Now, for the actual repro:
- Select Run/Debug - prompts with text below:
Run/Debug feature requires Java language server to run in Standard mode. Do you want to switch it to Standard mode now?
- Select Yes.
Intellisense is now completely broken, only capable of making raw-text suggestions based on common code-strings within the file.
Project experiencing the error: https://github.com/AlphaTiles/AlphaTilesEditor
- Happens whether or not a launch.json file (for run/debug launch configurations) is present.
A zip of the language server's .log file
- This one seemed to have more interesting detail, providing the excerpt seen earlier in this issue.
Current Result
Any use of Run/Debug necessitates a restart of the VS Code client in order to re-enable Intellisense.
Just to be clear, it doesn't matter whether or not the underlying type is from the JavaFX library, which would require an extra extension (see: JavaFX support); it even breaks for the basic String type.
Expected Result
Use of Run/Debug should have no impact whatsoever on Intellisense's ability to work.
Additional Informations
After trying a few more things to see if I could narrow down possible issues... I managed to somehow break the reset. The language server's no longer resetting to LightWeight mode for me, which is really disappointing.
Project details:
- Uses Gradle to build; is still a normal Java app, not an Android one.
- Uses JavaFX 11.0.1, which admittedly doesn't perfectly match the environment's JDK. Would prefer to support Java versions as old as 11 if possible, given that 11 is the latest LTS version of the OpenJDK.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne damit, das Zurücksetzen eines sauberen Arbeitsbereichs zu reproduzieren, über Run/Debug von LightWeight in den Standardmodus zu wechseln und die angehängten Language-Server-Protokolle auf den Fehler bei der Auflösung von ICompilationUnit zu prüfen. Vergleiche das Verhalten mit und ohne launch.json im verknüpften Gradle-Projekt; abgeschlossen ist die Aufgabe, wenn IntelliSense nach dem Moduswechsel weiterhin funktioniert, ohne VS Code neu zu starten.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java, typescript, vscode
- Bereich
- developer-experience, devtools
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100