Repository navigation
"Incomplete classpath" warning in https://github.com/redhat-developer-demos/istio-tutorial #686
Description
@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.
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.