noDaemon not supported in native mode
- Dominant language
- Java
- Stars
- 3.5k
- Forks
- 250
- Avg merge
- 16h 22m
- Merged PRs (30d)
- 36
Description
```
$ mvnd install -Dmvnd.noDaemon=true
Exception in thread "main" java.lang.UnsupportedOperationException: The mvnd.noDaemon property is not supported in native mode.
at org.mvndaemon.mvnd.client.DaemonConnector.connectNoDaemon(DaemonConnector.java:126)
at org.mvndaemon.mvnd.client.DaemonConnector.connect(DaemonConnector.java:93)
at org.mvndaemon.mvnd.client.DefaultClient.execute(DefaultClient.java:245)
at org.mvndaemon.mvnd.client.DefaultClient.main(DefaultClient.java:112)
```
Would be great to have at least a fallback not "leaking" a daemon when used (even if it is about starting a daemon and killing it at the end)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with org.mvndaemon.mvnd.client.DaemonConnector.connectNoDaemon and connect, then trace the call from DefaultClient.execute shown in the stack trace. Define the supported native-mode fallback and verify that mvnd install -Dmvnd.noDaemon=true completes without leaving a daemon running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100