Closed Vampire closed 1 year ago
Yes, the plugin has switched to properties long time ago and probably: https://github.com/szpak/gradle-pitest-plugin/blob/c97fe8a7575674681badf5489712973effecd6a0/src/main/groovy/info/solidsoft/gradle/pitest/PitestPlugin.groovy#L110
generates that warning. I will have to switch to JavaPluginExtension
. Thanks for pointing it out.
Yes, that's the place
Unfortunately, the sourceSets
were added to JavaPluginExtension
in Gradle 7.1, but the plugin is 6.4 compatible :-/
I had to use the conditional logic + dynamic features of Groovy to handle that. One the CD process is migrated from maven
to maven-publish
, it will be possible to drop support for Gradle <7.1.
Sorry, bad advice by me.
Just use the extension of type SourceSetContainer
with name sourceSets
on the project
.
That was there in 6.4 and is still in 8.2.
Just use the extension of type SourceSetContainer with name sourceSets on the project.
Cool, I didn't know SourceSetContainer
is an extension. Thanks!
That's why you can directly use top-level sourceSets { ... }
in a build script if the JVM ecosystem plugin is applied. :-)
Implemented in 1.15.0.
If you use the plugin on Gradle 8.2 you get warnings, that
Project.getConvention()
is deprecated and will be removed in Gradle 9. As the plugin anyway requires Gradle 6.4+ and the Java plugin convention was replaced by the Java plugin extension in 4.10 already, it should be a quite straightforward change without conditional execution necessary.