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

[anazar2001]

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

• Operating System: Darwin arm64 21.1.0
• JDK version: Zulu 8.60.0.21-CA-macos-aarch64
• Visual Studio Code version: .68.1 (https://github.com/microsoft/vscode/commit/30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:48:37.209Z)
• Java extension version: 1.8.0

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

[fbricon]

Looks like a regression in 1.8.0. Can you reinstall 1.7.0 and check if it still works?

[fbricon]

looks like m2e's choking with me.qoomon:maven-git-versioning-extension:3.3.1-mcv somehow. Can you provide sample projects reproducing this issue?

[anazar2001]

It is a proprietory project in Mastercard. Small to medium size Java maven project. Nothing special about it. And actually it is the same on many other projects too. Can't share it(( Where can I get 1.7.0?

[fbricon]

[anazar2001]

Thank

Thank you but I am using VS Code on my Macbook and interface looks slightly different - can't see where I can choose a different version. Any idea?

[fbricon]

I'm also on mac

https://user-images.githubusercontent.com/148698/177535341-e3f66b3d-2c7c-42be-8959-6c63f8508372.mp4

[anazar2001]

I'm also on mac

Jul-06-2022.12-54-21.mp4

My VS Code looks different. Please take a look

[fbricon]

Ah right, for some reason Mac M1s get a different build. You can still install 1.7.0 manually from https://github.com/redhat-developer/vscode-java/releases/download/v1.7.0/[email protected]

[anazar2001]

How can I install it? I downloaded it. Trying to open it. Mac asks for app, I select VS Code but it tries to open it as a text and asks for what editor to use.

How can I install it? I downloaded it. Trying to open it. Mac asks for app, I select VS Code but it tries to open it as a text and asks for what editor to use.

[anazar2001]

Figured it out. Works now. No errors in the log. Thank you a lot!!!

Do you think it could be fixed in 1.9.0?

[fbricon]

Need to investigate, possible regression with m2e. Having minimal test projects to reproduce would certainly help

[anazar2001]

Hi Fred,

Any idea when this issue will be fixed? Can see that 1.9 still has the bug. So could not update to it. Now I am 2 versions behind(((

Thanks, Andrei.

On Wed, 6 Jul 2022, 17:29 Fred Bricon, @.***> wrote:

Need to investigate, possible regression with m2e. Having minimal test projects to reproduce would certainly help

— Reply to this email directly, view it on GitHub https://github.com/redhat-developer/vscode-java/issues/2545#issuecomment-1176431716, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJXPJZ5O3KJUZFQWG6A7YLVSWYABANCNFSM52ZELL7A . You are receiving this because you authored the thread.Message ID: @.***>

[yorkish]

I can confirm that the issue is """resolved""" when I backtrack to version 1.7.0 of the extension. Running RockyLinux 8.5 + VsCode 1.70.2

[anazar2001]

Yes, it works with 1.7. But it needs to be fixed in the latest version too. When can it be done? It is clearly a regression.

On Tue, 30 Aug 2022, 22:33 yorkish, @.***> wrote:

I can confirm that the issue is """resolved""" when I backtrack to version 1.7.0 of the extension. Running RockyLinux 8.5 + VsCode 1.70.2

— Reply to this email directly, view it on GitHub https://github.com/redhat-developer/vscode-java/issues/2545#issuecomment-1232192492, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJXPJYUBKSJQMX23EBDM2LV3Z44BANCNFSM52ZELL7A . You are receiving this because you authored the thread.Message ID: @.***>

[snjeza]

A related issue - https://github.com/redhat-developer/vscode-java/issues/2647

[anazar2001]

Any updates on this? Even downgrade of java extension to 1.7.0 stopped working. Now using 1.11.0. Cleaned workspace many times. With multiple projects in workspace they are loading forever. If I remove all projects except one and restart VsCode, it works. I can even add another project and VsCode is not getting stuck. But if I restart VsCode again it loads indefinitely.

With 1.7.0 of java extension I stopped getting Testing tab visible and junit tests not recognised even for one single project. So it seems 1.7.0 is not compatible with the rest of the latest VsCode. So had to upgrade to 1.11.0 as it is a less bad.

I need to get it fixed as it really makes my work difficult.

The error I am getting in the Vs Code log:

!STACK 1 org.eclipse.core.runtime.CoreException: container creation failed at org.eclipse.m2e.core.internal.embedder.PlexusContainerManager$ExceptionalLookup.throwException(PlexusContainerManager.java:362) at org.eclipse.m2e.core.internal.embedder.PlexusContainerManager$ExceptionalLookup.lookup(PlexusContainerManager.java:350) at org.eclipse.m2e.core.internal.IMavenToolbox.lambda$2(IMavenToolbox.java:109) at java.base/java.util.Optional.map(Unknown Source) at org.eclipse.m2e.core.internal.IMavenToolbox.locatePom(IMavenToolbox.java:107) at org.eclipse.m2e.core.embedder.MavenModelManager.readMavenModel(MavenModelManager.java:122) at org.eclipse.m2e.core.project.LocalProjectScanner.readMavenProjectInfo(LocalProjectScanner.java:126) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:95) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.run(LocalProjectScanner.java:66) at org.eclipse.jdt.ls.core.internal.managers.MavenProjectImporter.getMavenProjects(MavenProjectImporter.java:302) at org.eclipse.jdt.ls.core.internal.managers.MavenProjectImporter.collectMavenProjectInfo(MavenProjectImporter.java:148) at org.eclipse.jdt.ls.core.internal.managers.MavenProjectImporter.getMavenProjectInfo(MavenProjectImporter.java:141) at org.eclipse.jdt.ls.core.internal.managers.MavenProjectImporter.importToWorkspace(MavenProjectImporter.java:164) at org.eclipse.jdt.ls.core.internal.managers.ProjectsManager.importProjects(ProjectsManager.java:149) at org.eclipse.jdt.ls.core.internal.managers.ProjectsManager.initializeProjects(ProjectsManager.java:111) at org.eclipse.jdt.ls.core.internal.handlers.InitHandler$1.runInWorkspace(InitHandler.java:244) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:43) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) Caused by: org.codehaus.plexus.classworlds.realm.DuplicateRealmException: coreExtension>me.qoomon:maven-git-versioning-extension:3.3.1-mcvl at org.codehaus.plexus.classworlds.ClassWorld.newRealm(ClassWorld.java:73) at org.apache.maven.cli.internal.BootstrapCoreExtensionManager.createExtension(BootstrapCoreExtensionManager.java:124) at org.apache.maven.cli.internal.BootstrapCoreExtensionManager.resolveCoreExtensions(BootstrapCoreExtensionManager.java:112) at org.apache.maven.cli.internal.BootstrapCoreExtensionManager.loadCoreExtensions(BootstrapCoreExtensionManager.java:92) at org.eclipse.m2e.core.internal.embedder.PlexusContainerManager.loadCoreExtensions(PlexusContainerManager.java:305) at org.eclipse.m2e.core.internal.embedder.PlexusContainerManager.newPlexusContainer(PlexusContainerManager.java:198) at org.eclipse.m2e.core.internal.embedder.PlexusContainerManager.aquire(PlexusContainerManager.java:165) at org.eclipse.m2e.core.internal.embedder.PlexusContainerManager.getComponentLookup(PlexusContainerManager.java:190) at org.eclipse.m2e.core.embedder.MavenModelManager.readMavenModel(MavenModelManager.java:120) ... 22 more !SUBENTRY 1 org.eclipse.m2e.core 4 0 2022-10-02 02:46:44.867 !MESSAGE container creation failed !STACK 0 org.codehaus.plexus.classworlds.realm.DuplicateRealmException: coreExtension>me.qoomon:maven-git-versioning-extension:3.3.1-mcvl at org.codehaus.plexus.classworlds.ClassWorld.newRealm(ClassWorld.java:73) at org.apache.maven.cli.internal.BootstrapCoreExtensionManager.createExtension(BootstrapCoreExtensionManager.java:124) at org.apache.maven.cli.internal.BootstrapCoreExtensionManager.resolveCoreExtensions(BootstrapCoreExtensionManager.java:112) at org.apache.maven.cli.internal.BootstrapCoreExtensionManager.loadCoreExtensions(BootstrapCoreExtensionManager.java:92) at org.eclipse.m2e.core.internal.embedder.PlexusContainerManager.loadCoreExtensions(PlexusContainerManager.java:305) at org.eclipse.m2e.core.internal.embedder.PlexusContainerManager.newPlexusContainer(PlexusContainerManager.java:198) at org.eclipse.m2e.core.internal.embedder.PlexusContainerManager.aquire(PlexusContainerManager.java:165) at org.eclipse.m2e.core.internal.embedder.PlexusContainerManager.getComponentLookup(PlexusContainerManager.java:190) at org.eclipse.m2e.core.embedder.MavenModelManager.readMavenModel(MavenModelManager.java:120) at org.eclipse.m2e.core.project.LocalProjectScanner.readMavenProjectInfo(LocalProjectScanner.java:126) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:95) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.scanFolder(LocalProjectScanner.java:111) at org.eclipse.m2e.core.project.LocalProjectScanner.run(LocalProjectScanner.java:66) at org.eclipse.jdt.ls.core.internal.managers.MavenProjectImporter.getMavenProjects(MavenProjectImporter.java:302) at org.eclipse.jdt.ls.core.internal.managers.MavenProjectImporter.collectMavenProjectInfo(MavenProjectImporter.java:148) at org.eclipse.jdt.ls.core.internal.managers.MavenProjectImporter.getMavenProjectInfo(MavenProjectImporter.java:141) at org.eclipse.jdt.ls.core.internal.managers.MavenProjectImporter.importToWorkspace(MavenProjectImporter.java:164) at org.eclipse.jdt.ls.core.internal.managers.ProjectsManager.importProjects(ProjectsManager.java:149) at org.eclipse.jdt.ls.core.internal.managers.ProjectsManager.initializeProjects(ProjectsManager.java:111) at org.eclipse.jdt.ls.core.internal.handlers.InitHandler$1.runInWorkspace(InitHandler.java:244) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:43) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

[yorkish]

What changed between 1.7.0 and 1.8.0 that caused this regression ?

[yorkish]

So nobody is working with 2 or more java projects in the same workspace or isn't using VS Code to do it ?!

[anazar2001]

Actually, I think the issue was fixed intentionally or not. A couple of versions ago. I have 10+ projects in my workspace. Loading is slow but once all is loaded it works.

[yorkish]

I'll give it another try

Le lun. 16 janv. 2023, 18 h 22, Andrei @.***> a écrit :

Actually, I think the issue was fixed intentionally or not. A couple of versions ago. I have 10+ projects in my workspace. Loading is slow but once all is loaded it works.

— Reply to this email directly, view it on GitHub https://github.com/redhat-developer/vscode-java/issues/2545#issuecomment-1384666932, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC4YPVRZBIATXILX5R64NA3WSXJ3BANCNFSM52ZELL7A . You are receiving this because you commented.Message ID: @.***>

[snjeza]

I'll give it another try

@yorkish Could you provide a project example reproducing the error?