Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Align tooling JDK validation and guidance with redhat.java 1.57.0 (JDK 25+)

Geschlossen
  • Stimmt etwas nicht?
#1,765 0 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@wenytang-ms arbeitet bereits daran.

Seit 08.10.2026.

  • #1768 von @wenytang-ms — offen

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
java, typescript, vscode
Bereich
developer-experience, tooling

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.java 1.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.java versions 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.
Vorherrschende Sprache
TypeScript
Sterne
355
Forks
165
Ø Merge
2 T. 14 Std.
Gemergte PRs (30 T.)
13

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/vscode-java-pack

Alle Issues in microsoft/vscode-java-pack

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

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