I notice sometimes when people use libraries that ...
# android
a
I notice sometimes when people use libraries that have annotation processing like Room, they have both
kapt "..."
and
annotationProcessor "..."
. What is the reason for needing both?
p
Ideally, annotation processors which are dealing with Java sources only wouldn't be part of the kapt. For example, there is no use case for applying @AutoValue on top of Kotlin classes. But that is not supported, at the moment everything has to be a kapt processor in mixed codebase suffering from performance (kapt disables incremental compilation)
👍 1