Please adopt task configuration avoidance.
It is present for a long time already and your plugin completely voids its time savings.
For example it uses tasks.all instead of tasks.configureEach which causes each and every task in the build to be realized and configured.
See https://docs.gradle.org/current/userguide/task_configuration_avoidance.html for more information.
.all might indeed by the only violation, at least from a very quick check I didn't see other violations.
You can also use Gradle build scans to see which tasks were realized at configuration time wich should optimally be 0.
Please adopt task configuration avoidance. It is present for a long time already and your plugin completely voids its time savings. For example it uses
tasks.allinstead oftasks.configureEachwhich causes each and every task in the build to be realized and configured. See https://docs.gradle.org/current/userguide/task_configuration_avoidance.html for more information..allmight indeed by the only violation, at least from a very quick check I didn't see other violations. You can also use Gradle build scans to see which tasks were realized at configuration time wich should optimally be 0.