Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#1,765 0 commentaires 1 réaction 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@wenytang-ms y travaille déjà.

Depuis le 8/10/2026.

  • #1768 par @wenytang-ms — ouverte

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
java, typescript, vscode
Domaine
developer-experience, tooling

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
TypeScript
Étoiles
355
Forks
165
Merge moyen
12 h 36 min
PR mergées (30 j)
9

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoft/vscode-java-pack

Toutes les issues de microsoft/vscode-java-pack

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.