Multiproject import go to other module method navigates to decompiled sources

[milic-marko]

Extension Name: vscode-gradle
Extension Version: 3.17.3
OS Version:
VSCode version: 1.116.0

Describe the bug
When navigating to method form other module in multimodlue gradle project, it navigates and opens decompiled source.

[github-actions]

Hi @mamilic, 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.

Suggested steps

• Open the root folder of your multi-module Gradle project in VS Code.
• In each dependent module’s build.gradle, declare inter-module dependencies explicitly, e.g.:

  dependencies {
    implementation project(':module-b')
  }

• In the Gradle view, click Refresh (or run Gradle: Refresh All).
• Run > Java: Clean the Java language server workspace, then reload the window.
• Verify that each sub-module appears under Java Projects. After this, “Go to Definition” should open your real source instead of a decompiled stub.

High-confidence reference

• Jump to source (symbol) in dependency – explains how JDT-LS resolves sources vs. decompiled code: jump to source (symbol) in dependency eclipse-jdtls/eclipse.jdt.ls#3534 (comment)

Other references with low confidence

• bug – javac can not reference class in other gradle module: a multi-module visibility issue in vscode-java bug - javac can not reference class in other gradle module redhat-developer/vscode-java#3885
• bug – changes are not propagated to java language server (multi-module sync issue) bug - changes are not propagated to java language server #1633

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!