when reruning builds (with gradle config cache one), I notice for every pure kotlin jvm project, thi...

# gradle

[ursus]

when reruning builds (with gradle config cache one), I notice for every pure kotlin jvm project, this task > Task :xyz:checkKotlinGradlePluginConfigurationErrors is ran always (i.e. not UP-TO-DATE)

What is it? It's a bug isn't it?

org.jetbrains.kotlin.gradle.plugin.diagnostics.CheckKotlinGradlePluginConfigurationErrors

kotlin 1.9.21, gradle 8.5

[wasyl]

For now it's working as intended unfortunately

https://youtrack.jetbrains.com/issue/KT-61931/checkKotlinGradlePluginConfigurationErrors-Gradle-task-is-never-up-to-date and https://youtrack.jetbrains.com/issue/KT-61943/Mark-the-checkKotlinGradlePluginConfigurationErrors-as-UP-TO-DATE-when-possible

[ursus]

oh well, thanks!

[diego-gomez-olvera]

I am getting an Android Studio Build Analyzer warning

Type: org.jetbrains.kotlin.gradle.plugin.diagnostics.CheckKotlinGradlePluginConfigurationErrors Duration: <0.1s

This task runs on every build because it declares no outputs, which it must do in order to support incremental builds.

pointing to https://developer.android.com/r/tools/build-attribution/no-task-outputs-declared

how far can affect incremental builds, I guess that just the CheckKotlinGradlePluginConfigurationErrors, right?

[wasyl]

fwiw this should be fixed soon https://youtrack.jetbrains.com/issue/KT-61943/Mark-the-checkKotlinGradlePluginConfigurationErrors-as-UP-TO-DATE-when-possible

[diego-gomez-olvera]

perfect, thanks!