build(deps): bump gradle-pitest-plugin from 1.4.0 to 1.9.0

[dependabot]

Bumps gradle-pitest-plugin from 1.4.0 to 1.9.0.

Release notes

Sourced from gradle-pitest-plugin's releases.

1.9.0

• PIT 1.9.4 by default (requires pitest-junit5-plugin 1.0.0!)
• Deprecate support for JDK 8 - #299
• Support for inputEncoding and outputEncoding (named in plugin inputCharset and outputCharset) - #310
• Add pitest dependencies only during configuration resolution - #313 - PR by Ian O'Malley
• Improve build cache hit cache with relative path - #315 - PR by Siddardha Bezawada
• Remove (optional) dependencyDistance configuration parameter removed in PIT 1.9.0 - #311

Compatibility notes

1. Due to the plugin API changes in PIT 1.9.0, the new pitest-junit5-plugin 1.0.0 is required (other PIT plugins - if used - also need to be upgraded).
2. The plugin is released with JDK 11. Source/class compatibility is still set to JDK 8, but this might change without notice.

1.7.4

• Do not pass --testPlugin for PIT 1.6.7+ for forward compatibility - #277
• Deprecate testPlugin configuration parameter (not needed in PIT 1.6.7+, to be removed in PIT 1.8.0) - #277
• PIT 1.7.4 by default
• Upgrade Gradle wrapper to 6.9.2
• Test for exclusion of certain mutators - #303 - PR by Narendra Pathai

Compatibility notes:

1. The testPlugin configuration parameter is deprecated and should not be used. In fact, starting with 1.6.7 it is no longer used (it is enough to add the PIT plugin as a buildscript dependency or just set junit5PluginVersion to use the JUnit 5 plugin). In addition, that property is planned to be removed in PIT 1.8.0.
2. Using junit5PluginVersion no longer internally set testPlugin property. For using with old PIT (<1.6.7) it is required to set it explicitly in configuration.

1.7.0

• Support for Gradle configuration cache - #249 - PR by David Burstrom
• Turn on cacheability for PitestTask - #67 - PR by David Burstrom
• PIT 1.7.0 by default
• Fix deprecation warnings in Gradle 7 - #283 - PR by Mike Duigou
• Bump minimal supported Gradle version to 6.4 - required to fix deprecation warnings in Gradle 7
• Remove unused maxMutationsPerClass configuration parameter - #266
• Regression tests for JUnit Jupiter 5.8 (with JUnit Platform 1.8) and pitest-junit5-plugin 0.15
• Upgrade Gradle wrapper to 6.9.1
• Switch CI from defunct travis-ci.org to travis-ci.com

Compatibility notes:

1. Gradle 6.4+ is required (to fix deprecation warnings in Gradle 7)
2. Not directly related with this plugin, but keep in mind that JUnit Jupiter 5.8 (JUnit Platform 1.8) requires pitest-junit5-plugin 0.15+, while 5.7 (1.7) requires <=0.14. Set right plugin version for JUnit 5 version used in your project to avoid runtime errors (such as NoSuchMethodError: 'java.util.Optional org.junit.platform.commons.util.AnnotationUtils.findAnnotation(java.lang.Class, java.lang.Class, boolean)' - see #300).
3. Due to the internal changes in PIT 1.7.0 (#630):
   • all history files should be deleted before upgrading
   • the names of the remove conditionals mutators have changed slightly (it might be needed to update their names in build.gradle, if activated explicitly)

1.6.0

• Report aggregation for multi-project builds - #243 - PR by Mike Safonov
• Support new configuration property testStrengthThreshold (PIT 1.6.1+) - #247 - PR by Michael Hönnig
• PIT 1.6.3 by default
• Regression tests also with Gradle 7 (milestone)
• Upgrade Gradle wrapper to 6.8.3
• Remove deprecated mutateStaticInits and includeJarFiles

... (truncated)

Changelog

Sourced from gradle-pitest-plugin's changelog.

1.9.0 - 2022-08-19

• PIT 1.9.4 by default (requires pitest-junit5-plugin 1.0.0!)
• Deprecate support for JDK 8 - #299
• Support for inputEncoding and outputEncoding (named in plugin inputCharset and outputCharset) - #310
• Add pitest dependencies only during configuration resolution - #313 - PR by Ian O'Malley
• Improve build cache hit cache with relative path - #315 - PR by Siddardha Bezawada
• Remove (optional) dependencyDistance configuration parameter removed in PIT 1.9.0

Compatibility notes

1. Due to the plugin API changes in PIT 1.9.0, the new pitest-junit5-plugin 1.0.0 is required (other PIT plugins - if used - also need to be upgraded).
2. The plugin is released with JDK 11. Source/class compatibility is still set to JDK 8, but this might change without notice.

1.7.4 - 2022-03-12

• Do not pass --testPlugin for PIT 1.6.7+ for forward compatibility - #277
• Deprecate testPlugin configuration parameter (not needed in PIT 1.6.7+, to be removed in PIT 1.8.0) - #277
• PIT 1.7.4 by default
• Upgrade Gradle wrapper to 6.9.2
• Test for exclusion of certain mutators - #303 - PR by Narendra Pathai

Compatibility notes:

1. The testPlugin configuration parameter is deprecated and should not be used. In fact, starting with 1.6.7 it is no longer used (it is enough to add the PIT plugin as a buildscript dependency or just set junit5PluginVersion to use the JUnit 5 plugin). In addition, that property is planned to be removed in PIT 1.8.0.
2. Using junit5PluginVersion no longer internally set testPlugin property. For using with old PIT (<1.6.7) it is required to set it explicitly in configuration.

1.7.0 - 2021-09-20

• Support for Gradle configuration cache - #249 - PR by David Burstrom
• Turn on cacheability for PitestTask - #67 - PR by David Burstrom
• PIT 1.7.0 by default
• Fix deprecation warnings in Gradle 7 - #283 - PR by Mike Duigou
• Bump minimal supported Gradle version to 6.4 - required to fix deprecation warnings in Gradle 7
• Remove unused maxMutationsPerClass configuration parameter - #266
• Regression tests for JUnit Jupiter 5.8 (with JUnit Platform 1.8) and pitest-junit5-plugin 0.15
• Upgrade Gradle wrapper to 6.9.1
• Switch CI from defunct travis-ci.org to travis-ci.com

Compatibility notes:

1. Gradle 6.4+ is required (to fix deprecation warnings in Gradle 7)
2. Not directly related with this plugin, but keep in mind that JUnit Jupiter 5.8 (JUnit Platform 1.8) requires pitest-junit5-plugin 0.15+, while 5.7 (1.7) requires <=0.14. Set right plugin version for JUnit 5 version used in your project to avoid runtime errors (such as NoSuchMethodError: 'java.util.Optional org.junit.platform.commons.util.AnnotationUtils.findAnnotation(java.lang.Class, java.lang.Class, boolean)' - see #300).
3. Due to the internal changes in PIT 1.7.0 (#630):
   • all history files should be deleted before upgrading
   • the names of the remove conditionals mutators have changed slightly (it might be needed to update their names in build.gradle, if activated explicitly)

1.6.0 - 2021-03-04

... (truncated)

Commits

• 6b810a2 Release version: 1.9.0
• 0826aa5 Trigger release
• 9546b93 Merge branch 'devel'
• f3f05d3 #299 Minor README update
• 9d83137 #299 Deprecate support for Java 8
• 0ab53f2 Update Gradle versions in regression tests
• 4e0ada8 Upgrade Spock to 2.2-M3
• de0cbcd Bump minor dependencies
• a4b4a73 #311 Remove dependencyDistance parameter
• c5e38de #310 Support for inputEncoding and outputEncoding
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #145.