Ability to override verbose from command line
#341
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@szpak what do you think about this addition? |
Pfoerd
force-pushed
the
set_verbose_from_cmdline
branch
from
6c99e25
to
940b833
Compare
Pfoerd
force-pushed
the
set_verbose_from_cmdline
branch
from
940b833
to
bede268
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When analyzing configuration failures of Pitest it's often necessary to temporarily turn on verbose output. Changing the configuration in gradle files is possible but obviously has some drawbacks.
This change adds the ability to turn on verbose output from the command line via an optional parameter:
./gradlew pitest --verboseFixes #349