From a4abdaa914ac9569035a034f4434e2c561f5425e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcin=20Zaj=C4=85czkowski?= <148013+szpak@users.noreply.github.com> Date: Sat, 26 Mar 2022 22:04:45 +0100 Subject: [PATCH] Adjust PIT gradle plugin configuration Starting with PIT 1.6.7 it is just enough to have kotest-extensions-pitest on (test) classpath Over more that parameter is already deprecated and "marked for deletion". See: https://github.com/hcoles/pitest/pull/900 https://github.com/szpak/gradle-pitest-plugin/issues/277 --- documentation/docs/extensions/pitest.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/docs/extensions/pitest.md b/documentation/docs/extensions/pitest.md index 6d5040d4931..cfd04c3538b 100644 --- a/documentation/docs/extensions/pitest.md +++ b/documentation/docs/extensions/pitest.md @@ -22,7 +22,7 @@ After doing that, we need to inform Pitest that we're going to use `Kotest` as a ```kotlin // Assuming that you have already configured the Gradle/Maven extension configure { - testPlugin.set("Kotest") // <-- Telling Pitest that we're using Kotest + // testPlugin.set("Kotest") // needed only with old PIT <1.6.7, otherwise having kotest-extensions-pitest on classpath is enough targetClasses.set(listOf("my.company.package.*")) } ```