-
Notifications
You must be signed in to change notification settings - Fork 58
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
@Option to enable export feature for PitestTask #139
Comments
I tried to implement it in a natural way - with an ability to override I don't know if I would like to implement any "hack" to just allow to enable Btw, unfortunately, the other plugin for configuration overriding also doesn't support collections: nebula-plugins/gradle-override-plugin#3 |
Just in case you don't know, Spock has a
Actually I wouldn't consider this a hack, but exactly what I wanted. |
Yes, I know I implemented |
I didn't test it yet, but from what I see in the commit, it looks nice, thanks :-) |
Since Gradle 4.6 you can add custom command-line flags for tasks using the
@Option
annotation.It would be nice if the
PitestTask
had such an option that enables theEXPORT
feature, so that you can decide on each run easily whether you want the mutants to be dumped on disk or not without having to edit the build script or implementing the logic using a project property in each build individually.The text was updated successfully, but these errors were encountered: