Repository navigation
Feature Request: Set default in java.configuration.runtimes to the workspace environment variable JAVA_HOME #1293
Description
Currently, the default of the Java extension java.configuration.runtimes is used as the default for No Build Tools, but it would be useful to set it to the environment variable JAVA_HOME which is valid for each workspace. The environment variable here is not the terminal, but process.env.JAVA_HOME, which is referenced by extensions such as
java.import.gradle.java.home
Setting > java.jdt.ls.java.home > JAVA_HOME > PATHmaven.terminal.customEnv
Setting > JAVA_HOMEjava.jdt.ls.java.home
Setting > Embedded JRE > JDK_HOME > JAVA_HOME > PATHspring-boot.ls.java.home
Setting > Embedded JRE > JAVA_HOME > PATHrsp-ui.rsp.java.home
Setting > JDK_HOME > JAVA_HOME> Windows Registry > PATHsalesforcedx-vscode-apex.java.home
Setting > JDK_HOME > JAVA_HOME> Windows Registry > PATHplantuml.java
Setting > PATH
The goal is to be able to use a different JAVA_HOME for each workspace, independent of the system's JAVA_HOME environment variable. For example:
User settings.json
"java.configuration.runtimes": [
{
"name": "JavaSE-17",
"path": "/path/to/java/17",
"default": true
},
{
"name": "JavaSE-21",
"path": "/path/to/java/21",
}
],Workspace settings.json (Override default runtime to JavaSE-21)
"java.configuration.runtimes": [
{
"name": "JavaSE-21",
"path": "/path/to/java/21",
"default": true
}
],java.configuration.runtimes is a Red Hat extension, but I am posting it here because I believe it needs to be supported by VSCode itself. It is related to the following issues.
#152806 API: allow an extension to change the environment variables
Activity
github-actions commentedon Nov 4, 2025
Hi Shinji Kashihara (@cypher256), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
Current state
java.configuration.runtimesat machine scope, so you cannot point the default to a workspace‐specificprocess.env.JAVA_HOMEtoday.Workarounds & tracking
You can set a workspace-specific
java.homein.vscode/settings.json, but it must be a literal path (no built-in support for${env:JAVA_HOME}in this setting).Track/upvote these feature requests:
• Per-project runtime override (proposed
java.project.runtime): java.configuration.runtimes in settings.json are ignored redhat-developer/vscode-java#2001 (comment)• Select Java runtime per workspace: feature request: select java runtime in vs code settings redhat-developer/vscode-java#1684
• Setting a different JDK version in a workspace: Setting a different jdk version in settings.json (workspace) redhat-developer/vscode-java#1431
Core VS Code API request to let extensions inject env vars: API: allow an extension to change the environment variables vscode#152806
Other references with low confidence
None
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!