redhat-developer / redhat-developer/vscode-java

More than one Java maven project is not displayed/resolved correctly in Java Projects view of multi root workspace in VS Code

Open
#2,545 21 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Maven regression
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

client.log
client_log2.log

Hi,

A couple of days ago noticed that when I add new java project It does not get resolved (classpath, JRE, etc) in Java Projects view. Hence Tests not working and in general it is not a java project for VS Code. If I remove the first project from the workspace then the second becomes a valid project.

I have the same laptop at home which is synced via github account for settings, extensions, etc and home laptop works fine but on small projects.

My work laptop periodically takes very long time to open Java projects (I have normally 5-7) in the workspace. When it can't within 2 min I just do cleanup workspace and after reload it can open, though still takes some time. This got worse over time. I already reinstalled vs code and cleaned all metadata. Did not help.

When project is not recognized as a Java project the tree node in java projects corresponding for this project is not expanding.

Could someone take a look and fix this as it is very annoying.

Thank you,
Andrei.

Environment
Steps To Reproduce
  1. Create a new workspace
  2. Import/Create new Java maven project
  3. Add to workspace a folder with a another Java maven project
  4. Check that the second project can be expanded and you can see packages, JDK, Maven dependencies, etc in Java Projects view.
  5. This does not happen for any 'second project'. Simple 'hello world' projects work sometime.
  6. If you remove the first project then the second gets displayed/handled properly.
    client.log

[Please attach a sample project reproducing the error]
Please attach logs

Current Result

Second, third, etc projects in the Multi root java workspace stopped working 2-5 days ago

Expected Result

Multiple Java projects should work in Multi root java workspace

Additional Informations

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the multi-root workspace from the listed steps with two or more Java Maven projects, then inspect the attached client.log files and the Java Projects view behavior. The fix is done when every project resolves its classpath, JRE, packages, and Maven dependencies and can be expanded without removing another project.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript, vscode
Domain
developer-experience, devtools, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.