Should not spawn a new daemon just for --help / --version
Open
enhancement
- Dominant language
- Java
- Stars
- 3.5k
- Forks
- 250
- Avg merge
- 16h 22m
- Merged PRs (30d)
- 36
Description
I was just building Quarkus with `mvnd` when I just wanted to check the `mvnd` options so I ran `mvnd --help` in another terminal.
I was surprised that a new daemon was spawned (other one was busy building Quarkus) just to print help, which seems a bit inefficient.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the behavior with `mvnd --help` and `mvnd --version` while another daemon is busy building. Trace the `mvnd` command entry point and its option handling to find where daemon startup occurs. Done means both informational options print their output without spawning a new daemon.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100