Changes in symbol processor does not invalidate compilation about ksp HOT 3 CLOSED

Some random update: Gradle does trigger the tasks correctly. It's the incremental compilation logic in kotlinc deciding that there is no source change and not triggering the processing and subsequent compilation. I'm trying to see how to inform kotlinc about the change.

from ksp.

We disabled incremental compilation when ksp is used as a workaround in android/kotlin#77. @yigit would that be a concern to you?

from ksp.

In my Kotlin compiler plugin I ran into the same issue. Since the compiler plugin comes with a Gradle plugin I fixed it there. I created a custom Gradle task that disables incremental compilation whenever the compiler plugin classpath contains a change, otherwise Kotlin compilation is incremental. That's better than always disabling incremental compilation.

The corresponding ticket is here: https://youtrack.jetbrains.com/issue/KT-38570

from ksp.