We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While running jps on my machine, it didn't immediately occur\ to me that ServerMain was the actual mvnd process.
jps
❯ jps 79547 ServerMain
I had to jstack it in order to find a meaningful classname in one of the stacktraces.
So just please make it so that the mvnd process can be immediately identifiable when browsing running processes.
The text was updated successfully, but these errors were encountered:
yes you can do jps -v to get more useful infos, without needing to dig into jstack
jps -v
Sorry, something went wrong.
OK, how about fbricon's favorite build tool ;)
fbricon's favorite build tool
Works for me
020c4ef
Merge pull request #120 from gnodet/issue-118
68b14f0
Rename ServerMain to MavenDaemon to be more explicit, fixes #118
No branches or pull requests
While running
jps
on my machine, it didn't immediately occur\ to me that ServerMain was the actual mvnd process.I had to jstack it in order to find a meaningful classname in one of the stacktraces.
So just please make it so that the mvnd process can be immediately identifiable when browsing running processes.
The text was updated successfully, but these errors were encountered: