Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No reuse of daemons, no build speedup. #261

Closed
PokingUrsa opened this issue Dec 15, 2020 · 3 comments · Fixed by #267
Closed

No reuse of daemons, no build speedup. #261

PokingUrsa opened this issue Dec 15, 2020 · 3 comments · Fixed by #267
Milestone

Comments

@PokingUrsa
Copy link

'Starting new daemon, 1 incompatible, 3 stopped'

Each time I invoke mvnd, it starts a new daemon, and there is no build speedup. How does it check for a compatible daemon?

OS: Ubuntu 20.04
AMD Ryzen Processor
Oracle 1.8.0 JDK

mvnd --version
mvnd native client 0.1.1-linux-amd64 (6e0a08b)
Terminal: org.jline.terminal.impl.PosixSysTerminal with pty org.jline.terminal.impl.jansi.linux.LinuxNativePty
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /home//mvnd-0.1.1-linux-amd64/mvn
Java version: 1.8.0_
, vendor: Oracle Corporation, runtime: ***
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-53-generic", arch: "amd64", family: "unix"

P.S. I would use mvnd even with no speedup because the build output is so improved!

@jjlharrison
Copy link

I'm seeing the same behaviour on Mac. Every run says that the daemon is either busy or incompatible.

@ppalaga
Copy link
Contributor

ppalaga commented Dec 15, 2020

Thanks for the report. Could you please briefly describe which mvnd commands with which options you issue? Are you switching directories, possibly going to fully independent source trees? Do you see anything interesting in the log files under .m2/mvnd/registry/*/?

@ppalaga
Copy link
Contributor

ppalaga commented Dec 15, 2020

Thanks, I was able to figure out what is the problem. The fix is underway.

@ppalaga ppalaga added this to the 0.2.0 milestone Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants