Closed khe817 closed 7 years ago
I have figured it out. There is nothing wrong with the debugger. There is a new launch configuration startupClassPathPattern
that I should use to make it debug normally.
My new launch.json:
{
"version": "0.2.0",
"configurations": [
{
"name": "Java Remote",
"jdkPath": "${env.JAVA_HOME}/bin",
"type": "java",
"request": "attach",
"stopOnEntry": true,
"cwd": "${workspaceRoot}",
"startupClass": "${relativeFile}",
"startupClassPathPattern": "src/main/java/",
"sourcePath": ["${workspaceRoot}/src/main/java"],
"classpath": ["${workspaceRoot}/target/classes"],
"remoteHost": "localhost",
"remotePort": 5005
}
]
}
@khe817 Your issues are very helpful, Thanks you for contribute! 👍
New released version of the debugger (0.1.4) broke something related to debugging multi-threaded processes.
Now to run the remote debugger for Spring Boot applications, I have to follow some extra steps:
F5
).Ctrl + Shift + F5
) once the application is started up & running. (<~~ This is the part where I supposed it's buggy, not sure if it's supposed to happen)F6
), then Run (F5
) the debugger again. (<~~ this one too)$ curl localhost:8080/greeting/
).My launch.json configurations are still the same as the one in issue #13 :
Pros is now I can attach and detach the debugger multiple times after the application starts up for debugging. I.e. I could edit the code, then run the debugger again without having to restart Spring Boot. Which is nice!