Suggestions for VSCode's Support for Java Language

未指定文件、测试或入口点；首先梳理 vscode-java-pack 中的 Java 扩展及其各自独立的 JDK 设置。将请求的项目级 JDK 选择与 issue 中描述的 Maven 和编译扩展行为进行比较。要视为完成，需要达成一致的核心配置，并证明受影响的扩展能够复用该配置。

The support for Java development in VSCode feels scattered without a core organization to regulate the development of other extensions generated for Java. The extensions available for Java in VSCode seem to be doing their own thing, and while some could define common standards to follow, there is no organization to establish that. As a result, each extension feels like a new entity. Even the configuration of the JDK cannot be unified.

JetBrains IDEA is also based on extensions, and many of its features are supported by different extensions. However, these extensions collaborate and embrace the parts that can be unified. Thus, IDEA is relatively more user-friendly.

For example, IDEA provides a unified JDK version selection option at the project level for users to choose from. The compilation extensions can select the JDK specified by the project rather than specifying a JDK version separately. The Maven plugin operates similarly when selecting the JDK, allowing direct selection of the JDK version chosen by the project.

The JDK that these extensions rely on can be specified uniformly, rather than configured separately.

The support for each language in VSCode should start with Microsoft defining a standardized core extension. In the case of the Java language, Microsoft should first define the configuration for the project's JDK. Other newly developed extensions that require a JDK should obtain this JDK option from the core extension.

There should be control over these global elements. Otherwise, every time a user installs an extension, they have to configure the JDK again. Even if configuration is manageable, the problem arises when a user's project needs to switch JDK versions. At that point, all Java extensions would have to re-specify the JDK configuration.

If the cohesion of these extensions is not considered globally, VSCode's development for the Java language will never improve, and no one will use VSCode to develop Java applications.

It is strongly recommended that Microsoft conduct in-depth research on the relevant features of JetBrains IDEA and draw from its more mature solutions to design within VSCode.