Ability to override verbose from command line
#341
Conversation
|
@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
|
Hi @szpak, any chance to get this released in the near future? We still have a great need for this :) |
|
A good question. I don't remember, why I didn't merge it back then 🤔 |
|
I've merged it into devel and it will be included in the next release. I have to do some housekeeping work before and in addition, due to the "recent" changes in Sonatype the releasing from CI might not work anymore. In the end in might take a moment to release. As a workaround, you might define something like: pitest {
verbose = project.findProperty("workaroundPitestVerbose") /*+ coercing string into boolean*/ ?: "false"
...in your build.gradle to be able to control it from the command line (probably you already have it defined that way ;-) ). Thanks for your PR. Sorry for delay (I might missed it (?), as it looks good and safe 🤔 ). |
|
No worries and thank you! You may also consider #350 for the next releases ;) |
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