-
Notifications
You must be signed in to change notification settings - Fork 644
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
the sledgehammer still exists during parallel execution runs #372
Comments
The ContainerTracker has been refactored to support PomLabels to only stop containerts stopped by a certain reactor project (identified via its Maven coordinates). + unit tests for container tracker.
Thanks for your PR. I picked up the idea, however did the implementation slightly different (by moving the burden to filtering on PomLabel into the ContainerTracker). 'hope thats ok for you. |
works for me - would it be possible to get a |
The ContainerTracker has been refactored to support PomLabels to only stop containerts stopped by a certain reactor project (identified via its Maven coordinates). + unit tests for container tracker.
Just released 0.13.9 with this change only :) since I still need a bit for 0.14.0 (where we possible should present docker compose support already). Thanks for the initial PR and kicking the wire. Also, I plan to move this repository to |
The ContainerTracker has been refactored to support PomLabels to only stop containerts stopped by a certain reactor project (identified via its Maven coordinates). + unit tests for container tracker.
The ContainerTracker has been refactored to support PomLabels to only stop containerts stopped by a certain reactor project (identified via its Maven coordinates). + unit tests for container tracker.
The ContainerTracker has been refactored to support PomLabels to only stop containerts stopped by a certain reactor project (identified via its Maven coordinates). + unit tests for container tracker.
if you run a reactor build in parallel, the plugin will stop any containers that get started during overall execution of the build.
The text was updated successfully, but these errors were encountered: