In multi-root workspace, it cannot exclude the project by using gradle.nestedProjects settings.

[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}",
// exclude the b.git
//      "${workspaceFolder:b.git}",
    ],
  },
}

Now, b.git will build failed, a.git will build successfully.
I find even exclude the b.git, the gradle for java still process it, and b.git will be shown in the sidear. What I can do is remove b.git from this multi-root workspace.

To Reproduce
Like above description.

Expected behavior
I want to exclude some project in one multi-root workspace, and don't show it in the sidebar, and not affect other projects.

Another related bug is #1784

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

Output from "Gradle for Java"
I can see the logs about processing b.git.

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 @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.

Suggestions to exclude a secondary Gradle project in a multi-root workspace:

• VS Code treats each workspace folder as its own Gradle build. The gradle.nestedProjects setting only applies to nested sub-projects within a single Gradle build, not to entirely separate workspace roots.

• To prevent b.git from being imported or built by the Java/Gradle tooling, add a .vscode/settings.json file in the b.git folder with:

  {
    "java.import.gradle.enabled": false,
    "java.gradle.buildServer.enabled": false
  }

  This disables both the Gradle import and the Gradle build server for that folder, so it won’t show up under Java projects or trigger builds.

• Hiding an entire workspace folder from the Explorer view isn’t currently supported (you’d need to remove it from the workspace or collapse it manually).

Other references worth checking:

• Issue: Disable one Java project from building in a multi-project workspace (#3749)
  • Describes a similar request to stop the language server from building an excluded project
  • URL: Add feature if it doesn't already exists: Disable one Java project from building and reporting compiler errors in VsCode workspace having multiple Java Projects. redhat-developer/vscode-java#3749

Other references with low confidence

• Issue: java.project.exclusion is not working as expected (#2075)
  • Reports problems with java.import.exclusions and negative patterns being ignored
  • URL: java.project.exclusion is not working as expected redhat-developer/vscode-java#2075

• Issue: java.import.exclusions being ignored for Eclipse projects (#2101)
  • Similar problem where import exclusions in a multi-root workspace aren’t honored
  • URL: java.import.exclusions being ignored for Eclipse projects on startup redhat-developer/vscode-java#2101

• Issue: In multi-root workspace, source paths of one project also contain paths of other projects (Bump powermock-module-junit4 from 2.0.7 to 2.0.9 #776)
  • Focuses on Java debug configuration but highlights multi-root exclusion challenges
  • URL: In multi-root workspace, source paths of one project also contain paths of other projects, should be excluded vscode-java-debug#776

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!