Closed christianhujer closed 4 years ago
Have you performed the steps mentioned in the release notes?
Next to the section "Compatibility changes".
That worked. And it's even nicer. The build.gradle
is better now. I just didn't expect a version change from 1.4.9
to 1.5.0
to require looking at the release notes and change my build.gradle
files.
That's why it was 1.5.0 not 1.4.10 :). Due to versioning scheme in PIT, it is somehow problematic to keep Semantic Versioning.
Btw, with 1.4.7+ you can simplify your JUnit 5 plugin configuration greatly: https://blog.solidsoft.pl/2020/02/27/pit-junit-5-and-gradle-with-just-one-extra-line-of-configuration/
When changing the PiTest Gradle plugin version from 1.4.9 to 1.5.0, PiTest stops working. The problem is that it can no longer load the JUnit 5 plugin.
Example project: https://github.com/nelkinda/template-java-gradle Steps to reproduce:
verbose = true
to thepitest{}
sectionmake && make pitest
Expected behavior: PiTest stops saying that no mutants were generated (there is no production code in the template project) Actual behavior: PiTest stops saying that it couldn't load the JUnit 5 plugin.