When the Java language server starts in lightweight mode, the project label info command (which is called when vscode-quarkus first starts) fails. Therefore the debug current quarkus project command (and add extensions command) will not appear in the command palette.
When the Java language server is switched to standard mode we still do not have those commands because the project labels command isn't triggered. The user would have to trigger it by adding or removing a workspace file:
|
const listener: Disposable = workspace.onDidChangeWorkspaceFolders(async () => { |
When the Java language server starts in lightweight mode, the project label info command (which is called when vscode-quarkus first starts) fails. Therefore the debug current quarkus project command (and add extensions command) will not appear in the command palette.
When the Java language server is switched to standard mode we still do not have those commands because the project labels command isn't triggered. The user would have to trigger it by adding or removing a workspace file:
vscode-quarkus/src/QuarkusProjectListener.ts
Line 38 in f38f4ca