spring-boot-devtools disables debugging, cannot hit breakpoints

Question

I am using devtools in spring-boot.

    <dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-devtools</artifactId>
        <scope>runtime</scope>
    </dependency>

I run in debugging mode, but I cannot hit any breakpoint, the v is missing from the breakpoint indicating the class has not loaded. If I remove the devtools dependency from POM, the breakpoints start hitting. Is there a way I can use devtools and hit the breakpoints also ?

This is how I run it in debugging mode :

Using the debug mode here.

On your application's main class or the `run` goal of Spring Boot's Maven plugin? — Andy Wilkinson, Feb 07 '18 at 10:50
If you're running it with Maven you're likely not running it with Devtools. — Makoto, Feb 07 '18 at 18:43
I don't know how, but I started hitting the breakpoints after I started it with debugging main class, then I started it in debug mode with maven goal, it worked. I am using devtools. It gives me the live-reload functionality when I run with maven. — Bhavya Arora, Feb 07 '18 at 19:06
The same is occurring to me, as soon as I add the dependency to `spring-boot-devtools`, breakpoints are not hit. I remove it, and breakpoints get back to work. — Jose Ospina, Oct 31 '18 at 14:46

Mateusz Nowakowski · Answer 1 · 2019-10-21T09:39:30.203

I had the same problem. I found a workaround. Use additional flag:

-Dspring-boot.run.fork=false

Possible cause(20.2 Automatic Restart): https://docs.spring.io/spring-boot/docs/2.1.9.RELEASE/reference/html/using-boot-devtools.html

As long as forking is enabled, you can also start your application by using the supported build plugins (Maven and Gradle), since DevTools needs an isolated application classloader to operate properly. By default, Gradle and Maven do that when they detect DevTools on the classpath.

spring-boot-devtools disables debugging, cannot hit breakpoints

1 Answers1