Currently a workspace generated with the vscode-project target contains two virtual folders at the root level: "Source root" and "Build artifacts". When working with multiple jdk repositories in multiple vscode instances, to distinguish them one needs to check absolute path of a file in the workspace to see which jdk folder and which build type is active.

I propose to include top-level folder name in the source root, to help distinguishing different vscode instances without having to check a file path. This works well if you keep different jdk workspaces in differently named folders such as jdk, jdk11u, jdk25u, jdk-custom etc.

This makes the Source root virtual folder in vscode read, e.g. for jdk25u: "Source root (jdk25u)".

Secondly, build artifacts can include the build configuration name in its name in the UI, becoming e.g. "Build artifacts (linux-x86_64-server-fastdebug)"