Bump gradle-pitest-plugin from 1.5.1 to 1.6.0

[dependabot-preview]

Bumps gradle-pitest-plugin from 1.5.1 to 1.6.0.

Release notes

Sourced from gradle-pitest-plugin's releases.

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

Sample configuration for the new report aggregation feature:

//in root project configuration
buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath 'info.solidsoft.gradle.pitest:gradle-pitest-plugin:...'
    }
}
apply plugin: 'info.solidsoft.pitest.aggregator' // to 'pitestReportAggregate' appear
subprojects {
apply plugin: 'info.solidsoft.pitest'
pitest {
    // export mutations.xml and line coverage for aggregation
    outputFormats = ["XML"]
    exportLineCoverage = true
    ...
}

}

After the pitest pitestReportAggregate tasks execution, the aggregated report will be placed in the ${PROJECT_DIR}/build/reports/pitest directory.

1.5.2

• Support java-test-fixtures plugin - #223 - PR by Piotr Kubowicz
• PIT 1.5.2 by default
• Add functional test with Spock 2 (using JUnit Platform)
• Bump minimal supported PIT version to 1.4.0 - the first version which required Java 8 (May 2018)
• Upgrade Gradle wrapper to 6.6

Changelog

Sourced from gradle-pitest-plugin's changelog.

1.6.0 - 2021-03-04

• 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

Sample configuration for the new report aggregation feature:

//in root project configuration
buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath 'info.solidsoft.gradle.pitest:gradle-pitest-plugin:...'
    }
}
apply plugin: 'info.solidsoft.pitest.aggregator' // to 'pitestReportAggregate' appear
subprojects {
apply plugin: 'info.solidsoft.pitest'
pitest {
    // export mutations.xml and line coverage for aggregation
    outputFormats = ["XML"]
    exportLineCoverage = true
    ...
}

}

After the pitest pitestReportAggregate tasks execution, the aggregated report will be placed in the ${PROJECT_DIR}/build/reports/pitest directory.

1.5.2 - 2020-08-18

• Support java-test-fixtures plugin - #223 - PR by Piotr Kubowicz
• PIT 1.5.2 by default
• Add functional test with Spock 2 (using JUnit Platform)
• Bump minimal supported PIT version to 1.4.0 - the first version which required Java 8 (May 2018)
• Upgrade Gradle wrapper to 6.6

Commits

• 22f4887 Release version: 1.6.0
• df085ac Trigger release
• 39956b0 Merge branch 'pr/247' into devel
• 447eee3 Simplify Travis cache management even more
• d9ea5f0 Simplify Travis cache management
• 431880c Improve validatePitestVersion task
• 5bc4c3d Enhance CHANGELOG
• 0ec43dc Bump project test dependencies
• d9a37a8 Remove deprecated configuration properties
• ef0b0bc Remove Idea warnings
• 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)