In multi-root workspace, if there is one project cannot be build, then other projects cannot see gradle tasks.

[leolcao]

Extension Name: vscode-gradle
Extension Version: 3.17.2
OS Version: Windows 11 25h2
VSCode version: 1.111.0

Describe the bug
Let's assume:

E:\a.git
E:\b.git
E:\a-b.code-workspace

In the workspace settings:

{
  "folders": [
    {
      "path": "a.git",
    },
    {
      "path": "b.git",
    },
  ],
  "settings": {
    "java.gradle.buildServer.enabled": true,
    "java.import.gradle.enabled": true,
    "gradle.nestedProjects": [
      "${workspaceFolder:a.git}",
      "${workspaceFolder:b.git}",
    ],
  },
}

Now, b.git will build failed, a.git will build successfully.
Open the gradle sidebar, I cannot see the gradle tasks and depedencies for the a.git project.

To Reproduce
Like above description.

Expected behavior
I want to see gradle tasks and depedencies from the a.git project even b.git is failed to build.

Screenshots
If applicable, add screenshots to help explain your problem.

Output from "Gradle for Java"
I can see the build failed for the b.git because some reason.

Does the bug still exist if you disable all other extensions?
Yes/No

Additional context
Add any other context about the problem here.

[github-actions]

Hi Leo Cao (@leolcao), 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.

Workarounds & Suggestions

• Exclude or fix the failing project from gradle.nestedProjects until its build errors are resolved. Tasks for a.git will load if b.git is not included in the scan.
• After fixing b.git, trigger a full refresh of Gradle tasks via the Command Palette → “Gradle: Refresh Gradle Tasks”.
• Enable verbose server logs to diagnose import issues:

  "java.trace.server": "verbose"

  Then inspect the Java Language Server output for errors in building b.git that may be blocking project discovery.

Relevant Issue

• Tasks not listed if Gradle sub-project opened in project’s directory
  Tasks not listed if Gradle sub-project opened in project's directory #1478
  (similar root vs subproject task discovery problem)

Other references with low confidence

• Multiroot workspace not working correctly with two invisible projects
  Multiroot workspace not working correctly with two invisibile projects redhat-developer/vscode-java#1183
  (JDT LS classpath incomplete in multi-root)

• Support composite builds
  Support composite builds #1661
  (feature request around Gradle composite builds)

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!