This message was deleted.

Most probably a classloading problem. The

KotlinCompile

class you search for in the init script is most probably not coming from the same class loader that is used to register the tasks in question. So as the classes come from different class loaders, they are technically different classes and you get no matches. You can easily verify by printing out the class loaders from the init script and from the task where it works. You might need to instead need to do something like

tasks.configureEach {
    if (it.class.name == "org.jetbrains.kotlin.gradle.tasks.KotlinCompile") {
        ...
    }
}

or something similar. Btw. do not do

tasks.withType(...) { ... }

, that totally prevents task-configuration avoidance. Always do

tasks.withType(...).configureEach { ... }

.

Thanks @Vampire for once again helping me out. I tried printing all of the

tasks

out, from both a

gradle

task

and an

init script

(as shown above). And both of them printed a quite a different set of tasks. You can see the difference here https://www.diffchecker.com/LA7U9InU/ Am I’m missing something about the lifecycle of

Gradle

here?

Do not use

tasks.all

though, except for trying things out / debugging. It completely circumvents task configuration avoidance, causing each and every task to be realized and configured eagerly and thus wasting your time.

Thanks for the heads up @Vampire, could you please suggest an alternative way of achieving the same behaviour. This is how my script looks so far:

allprojects {
    afterEvaluate {
        tasks.all {
            if (it.class.name.contains("org.jetbrains.kotlin.gradle.tasks.KotlinCompile")) {
                kotlinOptions {
                    freeCompilerArgs += ["-P", "...."]
                }
            }
        }
    }
}

Well, what I told you.

tasks.configureEach

, not

tasks.all

Got it @Vampire, thanks for the clarification.