redhat-developer / redhat-developer/vscode-java
Add support for workspace specific java.home that use vscode variables
Open
Nobody has claimed this yet.
enhancement
preferences
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
In the workspace specific settings.json,
Does not work:
"java.home": "${workspaceRoot}/java/jdk64"
Works:
"java.home": "D:/dev/proj-1/java/jdk64" works.
Environment
- Operating System: Windows
- JDK version: 8
- Visual Studio Code version: 1.31.1
- Java extension version: 0.38.0
Steps To Reproduce
- Open a workspace
- Create a folder named
.vscode - Create a file in the folder named
settings.json - Try the setting above that does not work by adding it to
settings.json
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior using the workspace-specific .vscode/settings.json file and the ${workspaceRoot}/java/jdk64 value on Windows with JDK 8. Compare it with the working absolute path, then trace how the Java extension reads java.home and resolves VS Code variables. Done means the workspace setting accepts the variable and uses the intended JDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100