redhat-developer / redhat-developer/vscode-java
How to modify the storage path of compiled files
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Can I modify the path where the compiled files are stored?
In my computer it is stored in C:\Users\Yuzu\AppData\Roaming\Code\User\workspaceStorage\eb62a0ae736135bbef9234e82128d501\redhat.java\jdt_ws\demo1_dece82a8\bin.
When I was creating multiple projects, I failed to clean up the compiled files in time, which caused the storage consumption of the system disk to increase, which I was very distressed. Can the compiled files be stored in the corresponding project root directory?
Environment
- Operating System: Windows 11 pro 22h2 22621.1992
- JDK version: OpenJDK 64-Bit Server VM (build 17+35-2724, mixed mode, sharing)
- Visual Studio Code version: 1.80.2
- Java extension version: v1.21.0
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
Begin by reproducing the Java extension's compiled-file placement on the reported Windows, JDK, and VS Code versions. Trace the workspace-storage behavior responsible for the path shown in the issue; no source file, entry point, or test is named. Done means the compiled files can be directed to a suitable project location or the supported configuration limitation is documented.
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
- 32/100