redhat-developer / redhat-developer/vscode-java
Corrupted workspace in Maven Multi-Module Project
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
[provide a description of the issue]
Environment
- Operating System: Windows
- JDK version: 1.8.0_172
- Visual Studio Code version: 0.25.0-insider
- Java extension version: 0.26.0
Steps To Reproduce
I fiddled with swagger, switched branches and got this:
message: The project was not built since the source file /jdt.ls-java-project/src/[SWAGGERJAVASOURCEPATHSHERE] could not be read
Additional Informations
I got this fixed after doing countless cleans and eclipse:eclipse by removing the vscode workspaceStorage alltogether.
I can't exactly tell you reproduction steps since its now fixed and i forgot to write down steps beforehand... but you should probably know that the language server / vscode-java compiler has issues with copied java source files referencing nonexistent source files in the workspaceStorage
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 reviewing how the Java language server and VS Code workspaceStorage handle Maven multi-module projects, branch switches, Swagger-related source references, and nonexistent source files. The report has no reliable reproduction steps or named files/tests; done should mean stale source references no longer leave the workspace corrupted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100