Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Should not spawn a new daemon just for --help / --version
See original GitHub issueI 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.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
gradle daemon keeps spawning · Issue #1099 - GitHub
I noticed that configuration of gradle wrapper has updated the daemon version to 6.4.1, and when building new spring boot project using ...
Read more >Error TT14000: TimesTen daemon internal error — oracle-tech
I had the TimesTen database on my computer for around 3 months. Everything was working fine, no problems at all.
Read more >The Gradle Daemon - Gradle User Manual
Currently, a given Gradle version can only connect to Daemons of the same version. This means the status output only shows Daemons spawned...
Read more >daemon(7) - Linux manual page - man7.org
A daemon is a service process that runs in the background and supervises the system or provides functionality to other processes. Traditionally, ...
Read more >Gradle build daemon disappeared unexpectedly (it may have ...
EDIT Looks like there has been a few changes with the new versions of Gradle. Since 3.0 you should not disable the daemon...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Right, I’d rather try to keep
mvndas much independent of the exact maven version in order to ease the migration or ideally, make it work with multiple versions. However, given we redefine theMavenDaemonClito override the default CLI already, I think that part is definitely dependent on the exact maven implementation and any change in the option supported by maven would require a change in that class, so I don’t see the caching of the formatted help output as a problem.It is doable, although not a priority for myself. Feel free to send a PR. BTW,
-v/--versionis a similar case.