I don't think this is supported because the idea is to detect the target environment that the project requires (eg. Maven project defines source/target of 11) and use the corresponding JVM for that. If there were multiple, then we would need to prompt each time to clarify which is actually intended in that case.

I believe https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-pack provides a UI over java.configuration.runtimes that makes it a bit easier to modify these options. See #2001 (comment) for a rough idea.

In #2001, we allowed projects to set their own java.configuration.runtimes . This allows having different runtimes for a particular Java version across projects. Not exactly what is requested here, but a step in that direction.

Allowing multiple jdk installation paths for the same environment name in our setting schema can be helpful. Because we cannot guarantee that the jdk scan logic can always find all jdk installations. If java.configuration.runtimes allows configure multiple JDKs for the same environment. User can set those JDKs at global level then this information can be shared across all workspaces.

Why not just registering all user set JDKs to the registration? In the case that there are multiple JDKs maps to the same environment, it is not necessary to use the environment name as the JDK name, we can generate a unique name for it.