Repository navigation
Java Projects view creates duplicate project entries when multiple projects from different locations are opened in one workspace #4478
Description
Activity
I can't seem to reproduce anything fishy. What are the artifact ids of the projects you're loading? Are they both "timestamp" ?
For multi folder workspaces, I see the first level has the folder name, and the second level has the artifact id name
For multi folder workspaces, I see the first level has the folder name, and the second level has the artifact id name
No, they are not both Java projects and they are not both
timestamp.My workspace contains two folders from two different filesystem locations:
- One folder is a d/projects/javaproject.
- The other folder is an d/frontend/angularproject.
For example:
Workspace ├── Java project -- D:\...\java-project │ │ └── Angular project -- D:\...\angular-projectOnly the Java project has a
pom.xmland MavenartifactId.The Angular project is a separate frontend project and does not have a Maven artifactId.
The issue I am seeing is that when both folders are opened in the same multi-folder workspace, the JAVA PROJECTS view becomes incorrect/duplicated and the project hierarchy does not correspond correctly to the workspace folders.
When I open the Java project alone, I don't see this behavior.
Could you please check how the Java Projects view handles a multi-folder workspace containing a Java project and a non-Java project such as Angular?
I can provide the exact folder structure and screenshots/logs if needed.
i mean first of all why you show Angular project in java projects ..?
Please see the attached screenshot where SagApkGen is the Angular project and genAicmaa is the Java project.
I hope this clarifies the exact scenario in which I am experiencing the issue.
Okay, I'll try that out
Yep, I was able to reproduce that using those steps. @wenytang-ms I saw that you were active on https://github.com/Microsoft/vscode-java-dependency , do you mind investigating this case?
Thank you for reproducing the issue.
Yes, please proceed with the investigation. I’ll be happy to provide any additional information, logs, or reproduction details if needed.
is there any progress....??
@datho7561 @wenytang-ms Just wanted to follow up on this issue. Please let me know if I can provide any additional logs or reproduction steps to help with the investigation.
I think @wenytang-ms would know how to do this better, since he's a regular committer on vscode-java-dependency, so I was hoping he'd respond here.
Thanks for the report. I confirmed this is an issue in Project Manager for Java rather than the Java language server.
I opened microsoft/vscode-java-dependency#1060 to track the fix. The problem is related to progressive project loading in multi-root workspaces.
Reacted by David ThompsonReacted by dlicois@angsag212223-svg
we shipped the new pre-release forvscode for java manager, please upgrade to0.27.2026082200to verify this issue. thanks!Hi,
I tested the latest pre-release version 0.27.2026082200, but the issue is still reproducible.
Steps to reproduce
Create/open a multi-root workspace.
Add two projects from different locations:
Project 1: Java/Maven project
Project 2: Angular project
Make sure both projects are added to the same workspace.
Open the Java Projects view.
Actual resultThe Angular project (syncfusion) is also appearing inside the Java Projects tree, even though it is not a Java/Maven project.
For example, my workspace contains:
Untitled (Workspace)
├── syncfusion ← Angular project
└── selenium ← Java projectBut the Java Projects view shows:
Java Projects
├── syncfusion ← ❌ Angular project incorrectly shown here
├── selenium
└── seleniumThe syncfusion project is an Angular project, not a Java/Maven project.
Expected result
The Java Projects view should only contain Java projects detected by the Java extension/project manager:
Java Projects
├── seleniumThe Angular project should remain available only in the normal Explorer view and should not appear in Java Projects or the Java project's Maven hierarchy.
Important detail
This happens when multiple folders/projects from different locations are opened in a single multi-root workspace.
I also tested the issue with the latest pre-release:
Project Manager for Java: 0.27.2026082200
The issue is still reproducible.
I have attached a screenshot showing the result.
Could you please let me know if there is any additional configuration or specific workspace structure you would like me to test?
2 remaining items
This makes it impossible to work with worktrees btw
@dlicois have you tried the latest prerelease of "Project Manager for Java"? From my testing, it should be resolved in that release.
@angsag212223-svg @dlicois if you can still reproduce the error after uninstalling "Project Manager for Java" then installing the latest prerelease, let us know. Otherwise, I'll close this issue.
I don't think it is working in my case.
I upgraded to 0.27.2026082200, and reopened the workspace.
I tried several workspace configuration :- project-a and project-a.worktrees paths in conf
- project-a and project-a.worktrees/feature.featxxx paths in conf
In both case only project-a is correctly built and detected in Java projects view. Others appear as empty nodes. When navigating to a java file in worktree project and using any kind of class navigation (ctrl+click), you are redirected to the other, detected java project.
Even with workspace cleaning.
The only wqy to have worktree project working was to only include this one and remove other projects of the same name.
In both case only project-a is correctly built and detected in Java projects view.
That's an unrelated issue. Your issue sounds like #4491.
The issue the original reporter was running into was that folders with no Java projects in them were reported as having a Java project in them. Do you have this issue?
Hi,
@datho7561
@wenytang-ms
I’m **Ravi Kumar Saini.
I’m currently on vacation due to Raksha Bandhan, so I won’t be able to perform the reproduction test right now. I’ll be able to test it on Monday and will update you with the results.Also, just to clarify, @angsag212223-svg is also my second GitHub account/ID.
I’m currently working on a browser-based IDE built with Eclipse Theia, and we’re also developing a custom IDE/software builder called GenCodeX. That’s why I initially encountered this issue while working with multi-root workspaces and Theia.
I’ll perform the test on Monday using a clean Java project and an Angular project from two different filesystem locations and let you know whether the issue is still reproducible.
If you need any additional information, logs, reproduction details, or any other help from my side, please feel free to connect with me at [rssaini7976@gmail.com](mailto:rssaini7976@gmail.com).
Thanks for your help and for investigating this!
Really appreciate you both taking the time to listen to and investigate this bug! 🙌
Thank you for reproducing the issue, discussing it, and working toward a fix. It genuinely means a lot to see the team taking community-reported issues seriously and putting effort into improving the developer experience. ❤️
I’m also really interested in the work you’re doing around VS Code, Theia, and the Java ecosystem. I’m currently working with Eclipse Theia and building a browser-based IDE and our own software builder IDE, GenCodeX.
I hope that, if there’s an opportunity in the future, I’ll get a chance to work with you and contribute to the project/community. It would be a great learning experience for me, and I’d be very happy to contribute wherever I can. 🚀
Thanks again for your time, support, and for listening to the bug report. Really appreciate it! 🙏
Reacted by wenyt@ravisaini79 @angsag212223-svg
do you try to validate this issue?Hi @wenytang-ms , yes, I have validated the issue again with the latest prerelease version of Project Manager for Java.
Unfortunately, I can still reproduce the issue. In my multi-root workspace, I have a Java/Maven project and an Angular project located in two different filesystem locations.
In the JAVA PROJECTS view, I can see the Java project appearing twice, in addition to the Angular workspace folder being displayed as an empty node.
So the duplicate Java project behavior still appears to be reproducible on my side.
I’ve attached the screenshot showing the current result. Please let me know if you need the exact workspace structure, logs, or a minimal reproduction project. I’d be happy to provide anything needed to help investigate this further.
Thanks again for looking into this! 🙏
@ravisaini79 Thanks for testing this again.
To clarify the scope of #4478, the issue fixed by microsoft/vscode-java-dependency#1061 was that Java project nodes could be duplicated or assigned to the wrong workspace folder during progressive project loading in a multi-root workspace.
In your latest screenshot, the two same-named entries represent different node types: the outer entry is the workspace-folder node, while the nested entry is the actual Java project node. They have the same label because the workspace folder and Java project use the same name. This is the expected hierarchy for a multi-root workspace and does not indicate that the Java project was imported twice.
The Angular workspace folder appearing as an empty node is separate behavior tracked by microsoft/vscode-java-dependency#758. If the remaining concern is that non-Java workspace roots should be hidden or expandable in the JAVA PROJECTS view, it would be better to continue that discussion in microsoft/vscode-java-dependency#758.
If you can reproduce two actual Java project nodes, or a Java project appearing under the wrong workspace folder, please provide a minimal reproducible workspace so we can investigate that specific behavior.
Reacted by John Snow@datho7561 The original duplicate/misassigned-project behavior tracked by this issue has been fixed by microsoft/vscode-java-dependency#1061.
The latest screenshot shows the expected
WorkspaceNode -> ProjectNodehierarchy. The remaining empty non-Java workspace-root behavior is a separate concern tracked by microsoft/vscode-java-dependency#758.Given that the issue originally reported in #4478 has been addressed, I think we can resolve this issue as completed.
Hii @wenytang-ms
Thanks for the clarification and for looking into this.
The first major issue regarding the duplicated/misassigned Java project nodes is now resolved. I understand that the two same-named
SSR_finaleentries are different node types: the outer one is the workspace-folder node and the nested one is the actual Java project node.Also, thanks for pointing out the Angular workspace-folder behavior. I’ll handle that separately under [microsoft/vscode-java-dependency#758](microsoft/vscode-java-dependency#758).
One additional point I noticed, which I consider low priority, is that when the workspace folder name and Java project name are identical, the
JAVA PROJECTSview displays the project name twice:Current:
Java Projects └── SSR_finale └── SSR_finale ├── src/main/java ├── src/main/resources └── src/test/javaExpected / cleaner:
Java Projects └── SSR_finale ├── src/main/java ├── src/main/resources └── src/test/javaI understand this is not a duplicate Java project, so I’m only mentioning the repeated name as a possible low-priority UI/UX improvement.
Thanks again for your help and clarification.
I think I'll close this issue for now, since it seems like the original issue has been addressed, and lets track the empty folder issue using the linked bug report in vscode-java-dependency.
@ravisaini79 Thanks for the feedback. The two nodes have different purposes: the outer node is the VS Code workspace folder, and the nested node is the Java project.
A workspace folder can contain multiple Java projects, so we cannot generally merge these levels. Handling only the same-name case would add an inconsistent special case and could make other layouts less clear.
Since this does not affect project detection or navigation, we will keep the current behavior for now.
Description
I am facing an issue with the Red Hat Java extension where the JAVA PROJECTS view shows duplicate/inconsistent project entries when multiple Java projects from different filesystem locations are opened in the same workspace.
Steps to reproduce
For example:
When the projects are opened together, the Java Projects tree can show duplicate project entries or an incorrect hierarchy.
Example:
Expected behavior
Each Java project should appear only once and should be associated with its correct project/workspace location.
Actual behavior
The same Java project can appear multiple times in the JAVA PROJECTS tree, and the hierarchy can become inconsistent.
The issue is especially noticeable when the projects are located in different filesystem locations. When projects are located under the same location, I do not observe the issue.
Additional information
I initially observed this issue in an Eclipse Theia-based editor using the Red Hat Java extension. I then reproduced the same behavior in standard VS Code as well.
Therefore, the issue does not appear to be specific to my Theia implementation.
I also observed related errors while opening files/projects, including:
and:
Could you please investigate whether this is related to Java project identification/project URI handling or the Java Projects TreeDataProvider when multiple workspace folders/projects are present?
I can provide extension logs, JDT LS logs, workspace configuration, and a minimal reproduction project if required.