Daemons are not stopped when execution is finished
- Dominant language
- Java
- Stars
- 3.5k
- Forks
- 250
- Avg merge
- 16h 22m
- Merged PRs (30d)
- 36
Description
### 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 ;-)
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue by running mvnd spring-boot:run, stopping it, and checking whether the daemon still holds the application port; compare this with mvnd --stop. Trace the daemon lifecycle from the mvnd command entry point through execution completion. Done means stopping the launched application also releases the daemon and its port without requiring a separate manual stop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100