Is there anything like gradle-java plugin's "Compile avoidance" planned for gradle-kotlin plugin?

Gradle 3.4 introduced a feature called Compile Avoidance, which would totally skip rebuilding gradle modules which have non-ABI-breaking changes.

Is there something like this planned for kotlin-gradle-plugin?

1 Like

Would also love an update on this. My kotlin sub modules always wholesale re-compile, even if not a single line of code was changed in my main module

Ok update on my own question: turning kotlin incremental building off with kotlin.incremental=false in gradle.properties somehow activated compilation avoidance.

Ok update on my own question: turning kotlin incremental building off with kotlin.incremental=false in gradle.properties somehow activated compilation avoidance.

That does not make sense.

I have tested changing some line in a private method (just a println) and compileKotlin is always triggered for all submodules, javaCompile is not (in a multimodule project). Build scan says:

The task was not up-to-date because of the following reasons:
Input property ‘classpath’ file tr2-domain\build\classes\kotlin\main\com\tr2\entity\FirstPayment.class has changed.

So I guess it doesn’t support compiler avoidance at the moment. Can’t find if it’s in the roadmap or not