Hey, nice that you came back with a solution, this will really help other users who hit the same bug in a multi-project Gradle setup.
For future readers, here’s a quick summary:
- Upstream issue: Gradle multi-project import materializes internal build/libs jars into live JDT classpath · Issue #4399 · redhat-developer/vscode-java · GitHub
- Workaround: add
"java.jdt.ls.scalaSupport.enabled": falsetosettings.jsonor to.code-workspace
The recent Scala-in-Gradle support in redhat.java adds extra jar entries to the classpath during import. Disabling this feature brings back the normal project reference behavior until the upstream fix lands.
I’ll mark the thread as solved.