Daemons are not stopped when execution is finished

[Marco-Sulla]

Affected version

2.0.0-rc-3 and 1.0.3

Bug description

When I launch mvnd, the daemon it creates doesn't stop once the program finishes its duty.

I discovered it because I set mvnd as default built tool in Intellij Idea. This way it's impossible to run a spring boot up using mvnd spring-boot:run: if you stop it, the daemon is still alive and the port result as still used, so you can't restart the app. You have to manually do mvnd --stop. Really boring.

PS: mvnd is blazing fast, I love it.
PPS: fortunately, Intellij finally added Spring Boot in conf files, so I can run it in debug mode without using mvn[d]. Probably they feel the competition with VS Code ;-)

[ppalaga]

Thanks for the report, @Marco-Sulla. The fact that Maven Daemon does not exit after finishing a build task is much more a feature than anything else. It is intententionally designed in that way to save the time to boot a JVM, load and JIT-compile Maven core and plugin classes.

You probably mean that the spring-boot:run mojo (rather than Maven Daemon itself) does not exit when you think it should exit after you perform some action in IntelliJ?

Does the same scenario behave as expected when run it in a stock terminal? - i.e. when you run mvnd spring-boot:run and stop it with CTRL-C, then all of the following is true?

• The spring-boot:run mojo stops
• The SB app stops
• The port is not occupied anymore
• Maven daemon is still alive having status IDLE as shown via mvnd --status?