Better code navigation support for multi-module projects

[nickzhums]

Mentioned in user interview.
Seems like in current VS Code Java, if we have multiple POMs, and parent POM, sometimes jumping between different references is not available.

Also, user wants to have IDEA-like UX to show the usage stats of references of a particular class.

[F-6666]

// On explicit save, run fixAll source action. On auto save (window or focus change), run organizeImports source action.
"editor.codeActionsOnSave": {
"source.fixAll": "explicit",
"source.organizeImports": "always",
}

[github-actions]

Hi @nickzhums, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Suggestions for multi-module code navigation

• Open the root of your multi-module project (or add each module as a workspace folder) so the Java language server sees all POMs and cross-module references. See: Maven, several projects eclipse-jdtls/eclipse.jdt.ls#593
• Enable “workspace resolution” for Maven artifacts (similar to Eclipse/IDEA) via the VS Code Maven extension. Track or upvote the ongoing discussion here: Support "workspace resolution" like Eclipse/IntelliJ IDEA vscode-maven#778

IDEA-like usage stats

• Use “Find All References” (F12) or the Call Hierarchy view (Ctrl+Alt+H) to locate and count references manually. There’s no built-in aggregated usage chart yet; consider opening a feature request in the Java extensions.

Other references with low confidence

• Incorrect classpathentry with relative build.sourceDirectory (vscode-java#2216): Issue around Maven imports when source directories use “..” paths. May affect multi-module imports in edge cases. Incorrect value of classpathentry element in the .classpath file if in pom.xml the build.sourceDirectory is relative redhat-developer/vscode-java#2216

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!