Build Server doesnt work with multi root workspaces

[feribg]

Extension Name: vscode-gradle
Extension Version:
3.17.1
OS Version:
OSX 26.2
VSCode version:
Version: 1.107.1 (Universal)
Commit: 994fd12f8d3a5aa16f17d42c041e5809167e845a
Date: 2025-12-17T14:15:14.850Z (2 wks ago)
Electron: 39.2.3
ElectronBuildId: 12895514
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

Describe the bug
Create a workspace with 2 folders: one valid gradle project, one random
You no longer see build server logs and it doesn't get picked up. vscode downgrades to buildkit. If you open just the gradle root not as a multi root workspace, it all works fine.

No logs in Build Server to share as nothing shows up.

I tried various things including adding this in the .code-workspace:

"settings": {
        /* Force Build Server (BSP) */
        "java.gradle.buildServer.enabled": "on",
        
        /* 'true' is more reliable than an array for discovery in multi-root */
        "gradle.nestedProjects": true,

        /* Fixes the 'Project is not a build server project' error */
        "java.import.gradle.enabled": true
    }

and various other config attempts, but nothing works.

[github-actions]

Hi @feribg, 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

• Try specifying nested projects as an array of folders rather than a boolean. In your .code-workspace:

"gradle.nestedProjects": [
  "<relative-path-to-your-gradle-project>"
]

See Gradle extension settings for nested project discovery: https://github.com/microsoft/vscode-gradle#settings

• Make sure java.gradle.buildServer.enabled and java.import.gradle.enabled are set as booleans, e.g.:

"java.gradle.buildServer.enabled": true,
"java.import.gradle.enabled": true

• Enable verbose logging to diagnose why the BSP server isn’t starting:

"java.trace.server": "verbose"

Then check the “Java” and “Gradle for Java” output channels.

• As a temporary workaround, open only the Gradle project folder (single-root workspace). Multi-root support for the Gradle Build Server is still evolving.

High-confidence references

• Enhanced support of multi-root workspace (eclipse-jdt.ls) – tracks general multi-root issues in the Java build server:
eclipse-jdtls/eclipse.jdt.ls#1303

• More than one Java maven project not displayed in a multi-root workspace – similar multi-root issue in the Java extension:
redhat-developer/vscode-java#2545

Other references with low confidence

• ConcurrentModificationException when importing large multi-project Gradle build (BSP) – large build import bug:
redhat-developer/vscode-java#4043

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!

[feribg]

buildServer.enabled: Value is not accepted. Valid values: "on", "off".(1)

setting gradle.nestedProjects to ['projectName'] has no effect

[chagong]

@feribg where do you add that 'gradle.nestedProjects' settings? Try put it under '.vscode/settings.json'

[feribg]

@chagong no effect and also the config linter pretty explicitly states: This setting cannot be applied in this workspace. It will be applied when you open the containing workspace folder directly. so it expects it in the project workspace file i guess.

[chagong]

Can you make it this:

[feribg]

@chagong same issue, can you toggle in the dropdown Build Server for Gradle in the output rather than gradle for java, thats the one that needs to show output and doesn't in my case. The gradle for java shows the same as it does for you but is not the correct implementation.

[chagong]

There are output in 'build server for gradle (log)', if you are saying 'build server for gradle (build)' channel, I think it only shows log when you have some build errors.

[feribg]

@chagong yes that worked! thanks, so this works but when its a workspace and it has a few modules in it it doesnt work, only works when i open a "folder" outside of a workspace context and add the root .vscode/settings.json not sure why that is...

[chagong]

The 'workspace' here you mentioned is a vscode workspace that contains sub projects, do you? I think that's how the extension works, vscode itself can put folders anywhere into one workspace at the same time, but java extension needs to parse settings from root folder.