Does the Kotlin Gradle Plugin impact the container architecture (in
C4 Model terms, i.e. the runtime process architecture) of how Java sources are compiled by Gradle?
I know the KGP adds a single
KotlinCompileDaemon
process to the mix. Does that exclusively handle the compilation of Kotlin sources, or are
compileJava
tasks executed by that as well (instead of the usual Gradle Daemon/Worker processes)?
I'm trying to understand whether the standard Gradle suggestions and features for optimizing Java compilation, such as
forking `JavaCompile`
tasks, and the new
persistent Java compiler daemon feature, apply any differently when the Kotlin Gradle Plugin is used.
Just as background, I work primarily on a sizable project that mixes Java and Kotlin, and optimizing build times is a constant challenge. I currently apply the KGP to all my Gradle subprojects via a
convention plugin, regardless of whether they contain only Java, only Kotlin, or a mix of both.
