Double check Spring Boot dashboard behavior with launch.json

[nickzhums]

Per survey

“Sometimes it feels a little slow. Also it's not clear if starting application from the Spring Boot Dashboard will take into consideration configuration from the launch.json”

[github-actions]

Hi nickzhums, 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.

• The Spring Boot Dashboard uses the Java Debugger extension and simply passes your launch.json when starting an app. All settings—mainClass, vmArgs, env vars, and cwd—are honored. See: Spring Boot Dashboard - Setting for Cert store with VSCode extension vscode-spring-boot-dashboard#170 (comment)

• When you click “run” in the Dashboard, it will match an existing launch config by mainClass. If you experience slowness or spinning:
  • Remove or rename .vscode/launch.json
  • Launch again from the Dashboard to let a fresh config be generated
  • Compare the old config to spot malformed entries
  (ref: Spring boot Dashboard keep spinning vscode-spring-boot-dashboard#216 (comment))

Other references with low confidence

Additional notes

• If you omit mainClass, the Dashboard will scan all workspace (and even external) classes, which can delay startup. Defining mainClass+projectName speeds this up. If mainClass not specified, it will find main classes not belonging to current workspace.  vscode-java-debug#1098

• For multi-module projects or sub-folders, set cwd in your launch config to the correct folder. Dashboard starts submodules in wrong directory vscode-spring-boot-dashboard#71

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!