You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"Incomplete classpath" warning in https://github.com/redhat-developer-demos/istio-tutorial #686
@burrsutter reports that opening a java file under https://github.com/redhat-developer-demos/istio-tutorial shows the infamous incomplete classpath warning. Maven projects are detected though, as the max search depth is 5 and the server logs "Importing Maven project(s)". but any opened file reports that warning, long after the server has completed initialization.
My gut feeling is it's caused by all the Maven projects using the same "customer" artifactId. @burrsutter until we find a proper solution, I suggest you find different artifactIds for your projects.
@fbricon I can confirm your gut feeling. I have a workspace with 2 Maven projects with equal artifactIds (but different groupIds, of course): projectA has a pom packaging, projectB has a jar packaging.
When I put projectA first in the list of workspace folders, projectB shows the "Incomplete classpath" warning, and has errors in its module-info.java, saying it can't find required modules.
When I put projectB first in the list, and do a Java: Clean the Java language server workspace, projectB has no warnings/errors.
When I put projectA first in the list again, rename projectB's artifactId, and do a Java: Clean ... again, projectB remains without warnings/errors.
Hey @shin19991207 I've assigned this one to you to investigate. It's a pretty clear simple project, or you can create your own to try to replicate (same artifact id) and try to see what's going wrong.
It's possible it can't be fixed easily, but we definitely need some investigation as to where in m2e things are going wrong.
If you get a tiny simple pair of sample projects that can replicate it, I can donate some tokens once you narrow down where it might be coming from.
I investigated the case described by @anthonyvdotbe, where two workspace folders contain Maven projects with the same artifactId but different groupIds.
The collision occurs in the Eclipse project names. By default, m2e uses the artifactId, while Eclipse requires project names to be unique within a workspace. JDT.LS already selects [groupId]-[artifactId] when it detects duplicate artifact IDs in one import batch. However, separate workspace roots can be imported in separate batches, so that detection misses the collision. If the first project takes the name, the second cannot be imported normally. This can be worked around by configuring the java.import.maven.projectNameTemplate setting:
To address this without requiring users to configure the setting manually, I suggest simply making [groupId]-[artifactId] the default for Maven imports in JDT.LS, rather than using it only as a fallback when duplicates are detected within an import batch.
However, this would not resolve the https://github.com/redhat-developer-demos/istio-tutorial example, where alternative implementations of the same service share same group/artifact IDs. Those copies would still produce same qualified names and encounter the same naming collision. To cover that case as well, another option is to use path-derived Eclipse project names for Maven imports. This could distinguish separate copies with identical Maven coordinates without requiring a collision fallback. Though, it would need a consistent policy for path normalization, uniqueness across workspace roots, and handling projects that move .... (which could make the implementation more fragile?)
My preference is to make [groupId]-[artifactId] the default. I'm not sure how common it is to have multiple projects with identical group/artifact IDs in the same workspace beyond cases like the istio tutorial? so for that case, I would suggest opening one implementation at a time
Activity
anthonyvdotbe commentedon Apr 18, 2019
@fbricon I can confirm your gut feeling. I have a workspace with 2 Maven projects with equal artifactIds (but different groupIds, of course): projectA has a
pompackaging, projectB has ajarpackaging.Java: Clean the Java language server workspace, projectB has no warnings/errors.Java: Clean ...again, projectB remains without warnings/errors.robstryker commentedon Nov 2, 2026
Hey @shin19991207 I've assigned this one to you to investigate. It's a pretty clear simple project, or you can create your own to try to replicate (same artifact id) and try to see what's going wrong.
It's possible it can't be fixed easily, but we definitely need some investigation as to where in m2e things are going wrong.
If you get a tiny simple pair of sample projects that can replicate it, I can donate some tokens once you narrow down where it might be coming from.
shin19991207 commentedon Nov 18, 2026
I investigated the case described by @anthonyvdotbe, where two workspace folders contain Maven projects with the same
artifactIdbut differentgroupIds.The collision occurs in the Eclipse project names. By default, m2e uses the
artifactId, while Eclipse requires project names to be unique within a workspace. JDT.LS already selects[groupId]-[artifactId]when it detects duplicate artifact IDs in one import batch. However, separate workspace roots can be imported in separate batches, so that detection misses the collision. If the first project takes the name, the second cannot be imported normally. This can be worked around by configuring thejava.import.maven.projectNameTemplatesetting:{ "java.import.maven.projectNameTemplate": "[groupId]-[artifactId]" }To address this without requiring users to configure the setting manually, I suggest simply making
[groupId]-[artifactId]the default for Maven imports in JDT.LS, rather than using it only as a fallback when duplicates are detected within an import batch.However, this would not resolve the https://github.com/redhat-developer-demos/istio-tutorial example, where alternative implementations of the same service share same group/artifact IDs. Those copies would still produce same qualified names and encounter the same naming collision. To cover that case as well, another option is to use path-derived Eclipse project names for Maven imports. This could distinguish separate copies with identical Maven coordinates without requiring a collision fallback. Though, it would need a consistent policy for path normalization, uniqueness across workspace roots, and handling projects that move .... (which could make the implementation more fragile?)
My preference is to make
[groupId]-[artifactId]the default. I'm not sure how common it is to have multiple projects with identical group/artifact IDs in the same workspace beyond cases like the istio tutorial? so for that case, I would suggest opening one implementation at a time