Correct -Dstart-containers
guard so that it still works if -DskipTests
is set to false in container-image/maven-invoker-way
#25253
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does 3 things:
-Dstart-containers
guard so that it still works as intended if-DskipTests
is set to false on the command line-DskipTests
and-DskipITs
if-Dstart-containers
is set (so we won't suddenly launch ITs if-DskipITs=true
-Dstart-containers
rather than blanket OS bans), and we should avoid multiple conditions in profile activation since they'reOR
before mvn 3.2.2, andAND
after, which is just upsetting.