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
Sylvain Morin created PAXRUNNER-416
I want to launch 2 pax runner daemons with the same user, for continuous integration purpose.
The second instance failed, because the lock file is already created in : $user.home/.pax/
The path to the lock file cannot be changed with a propery (whereas it's possible for the password file, in the same class).
It's would be nice to configure the lock file path with the org.ops4j.pax.runner.daemon.lock property.
Affects: 1.7.6 Votes: 2, Watches: 1
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Sylvain Morin created PAXRUNNER-416
I want to launch 2 pax runner daemons with the same user, for continuous integration purpose.
The second instance failed, because the lock file is already created in : $user.home/.pax/
The path to the lock file cannot be changed with a propery (whereas it's possible for the password file, in the same class).
It's would be nice to configure the lock file path with the org.ops4j.pax.runner.daemon.lock property.
Affects: 1.7.6
Votes: 2, Watches: 1
The text was updated successfully, but these errors were encountered: