Align tooling JDK validation and guidance with redhat.java 1.57.0 (JDK 25+)
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- java, typescript, vscode
- Ambito
- developer-experience, tooling
Direzione di ricerca
Start with src/java-runtime/utils/upstreamApi.ts, src/java-runtime/assets/ToolingJDKPanel.tsx, and src/beginner-tips/assets/tabs/FaqPanel.tsx, then compare the runtime-selection behavior with the linked redhat.java resolver. Check existing tests for runtime validation and UI guidance. Done means readiness, displayed runtime information, and guidance consistently reflect the language server's JDK 25 minimum while preserving older project targets and compatibility with older extension versions.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
Align Java Pack's runtime validation, Configure Java Runtime UI, and beginner guidance with the JDK requirements and runtime-selection behavior of redhat.java 1.57.0.
The release adds Java 27 project support and requires JDK 25 or newer to launch the language server. These are different requirements: projects must not be forced to target Java 25 or Java 27.
Current behavior
Verified against Java Pack main at 0823dbde1947de111c39890fc095f55c0ff0d258:
- The runtime resolver still uses
REQUIRED_JDK_VERSION = 17. - The tooling JDK panel independently hard-codes the same minimum.
- The beginner FAQ also independently hard-codes 17.
- Java Pack's resolver is an older copy of the upstream resolution logic. It can treat an explicitly configured, under-minimum tooling JDK as valid, whereas the new language support extension rejects it for tooling and attempts to select a qualified runtime.
In contrast, the current language support resolver requires 25 and includes fallback handling for under-minimum configured runtimes.
This can make Java Pack's readiness checks and displayed tooling JDK disagree with the runtime that actually launches the language server. This report is based on source inspection; it is not a claim that every Java 27 project fails to launch.
Proposed scope
- Align tooling-runtime validation and selection with the installed language support extension's supported requirements, including explicit settings, bundled runtimes, and fallback discovery.
- Update all related UI and FAQ messages together, avoiding contradictory independently maintained minimums.
- Keep the tooling runtime separate from project runtimes. Older project targets must continue to work.
- Do not add a separate hard-coded Java 27 compiler-level list: the project settings UI already obtains supported levels from
redhat.java's runtime configuration schema.
Acceptance criteria
- With
redhat.java1.57.0, tooling readiness never reports an external JDK 17-24 as satisfying the language server's JDK 25 minimum. - When an under-minimum explicit tooling JDK is configured, displayed runtime/error information agrees with the language support extension's selection and fallback behavior.
- A valid bundled JDK 25 is recognized without requiring a separate JDK 27 installation just to launch the language server.
- JDK 25 and JDK 27 tooling installations are recognized correctly; supported older project runtimes remain configurable.
- Configure Java Runtime, the tooling JDK panel, and the FAQ present consistent requirements.
- Existing supported combinations with older
redhat.javaversions are considered when choosing how to obtain or version the minimum requirement.
Related
- Historical runtime-alignment work: microsoft/vscode-java-pack#787, which is closed and predates this new requirement.
- Language support release: vscode-java 1.57.0 changelog.
- Lingua principale
- TypeScript
- Stelle
- 355
- Fork
- 165
- Merge medio
- 2g 14h
- PR unite (30g)
- 13
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/vscode-java-pack
-
Memory Leak in LinuxApertaai-triaged bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
microsoft/vscode-java-pack#1543 · 8 commenti · 4 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
ai-triaged bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
microsoft/vscode-java-pack#1443 · 1 commento · 2 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
ai-triaged bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
microsoft/vscode-java-pack#1425 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
ai-triaged enhancement feature-request
Difficoltà 5/5 Più di una settimana Idoneità per principianti 20/100
microsoft/vscode-java-pack#1423 · 2 commenti · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
ai-triaged area/jdtls bug needs-investigation
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
microsoft/vscode-java-pack#1420 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di microsoft/vscode-java-pack
Issue simili
-
affected/v17 affected/v18 area/frontend type/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
umbraco/Umbraco-CMS#24186 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
better-auth/better-auth#11723 · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
area: docs difficulty: easy documentation good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Worker-Erstellung bricht langsame Git-Worktree-Checkouts nach 20 Sekunden abForse già presa @KajoVanBuyten l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 69/100
AgentSystemLabs/agent-office#367 ·
I maintainer di solito rispondono entro 1 giorno