Plugins should not use Gradle.buildFinished - Githubissues

nebula-plugins / gradle-dependency-lock-plugin

A plugin to allow people using dynamic dependency versions to lock them to specific versions.

Apache License 2.0

292 stars 42 forks source link

Plugins should not use Gradle.buildFinished #271

Open abstratt opened 2 months ago

abstratt commented 2 months ago

This was detected by Gradle's own smoke tests:

https://github.com/nebula-plugins/gradle-dependency-lock-plugin/blob/d9c5ceefe67f2b94ccb546f7b75320c29efe72a0/src/main/kotlin/nebula/plugin/dependencyverifier/DependencyResolutionVerifier.kt#L76

Gradle is in the process of deprecating Gradle.buildFinished and other build scope listeners (such as TaskGraphExecution.addTaskExecutionListener) starting in Gradle 8.10 (currently, it is only reported as a problem when configuration cache is enabled).

Instead of using Gradle.buildFinished, plugins should use "always" flow actions.