<@U8HCXRCT0> Actually, these 4 stages are: 1) stub...

# compiler

[yan]

@thalescm Actually, these 4 stages are: 1) stub generation 2) annotation processing 3) kt compilation 4) java compilation.
There is some documentation available in our website: https://kotlinlang.org/docs/reference/kapt.html#using-in-cli.
--debug is definitely a bit noisy. I think you can run with the --info option instead, it should also print all options passed to kotlinc.
As about incremental compilation, I think @alexey.tsvetkov can help you much better than me.

[thalescm]

--info does not print the options 😞

[yan]

Hm-m. Well, I got used to read --debug output, and, although it’s over-verbose, it’s not that hard to find the needed data by searching the substring (e.g. kapt).

[yan]

The one thing you should probably know though is that in newer Kotlin Gradle plugins kapt options are passed alltogether (and base64-encoded). So I think the earlier plugins (1.1.60) may be more useful for you.

[thalescm]

Yeah, I decoded them to see what it passes, it was basically (in a simple example) the kapt.kotlin.generated parameter to the right path