we're seeing this in our android build output. is it an us problem or a kotlin/kapt problem? ```The ...

# kapt

[Sha Sha Chu]

we're seeing this in our android build output. is it an us problem or a kotlin/kapt problem?

The following annotation processors are not incremental: kotlin-compiler-embeddable-1.7.10.jar (org.jetbrains.kotlin:kotlin-compiler-embeddable:1.7.10).
Make sure all annotation processors are incremental to improve your build speed.

[tapchicoma]

I will suspect something wrong with your build configuration. Create Gradle build scan and check kapt classpath

[Sha Sha Chu]

we do publish build scans (to an internal server). where do i look for the kapt classpath? (also hi Yahor 🙂 good to see you)

[tapchicoma]

hi 🙂

in dependencies tab check project that produces such warning - there should be a configuration with kapt in name. Generally kotlin-compiler-embeddable should not be in this configuration

[Sha Sha Chu]

ok i do see it in the kapt configuration. we have a module called processors that has all our custom annotation processors; i see the kotlin-compiler-embeddable in that module's kotlinCompileClasspath. we use it in other modules via kapt project(':library:processors') and i think that's how it's getting into the kapt config

[Sha Sha Chu]

should we be doing something differently?

[tapchicoma]

kotlinCompileClasspath is not publishable configuration so it will not affect/leak to consumers

[Sha Sha Chu]

hmm

[Sha Sha Chu]

.

[Sha Sha Chu]

total user error: someone recently added this as a dependency into one of our modules for some reason but I wasn't seeing it.