hello, just a hit a weird error -> I'm writing custom plugin that relies on coroutines 1.3. When ...

# gradle

[Dariusz Kuc]

hello, just a hit a weird error -> I'm writing custom plugin that relies on coroutines 1.3. When I try to apply it on a project and run my custom task I'm getting exception complaining

Caused by: java.lang.NoSuchMethodError: kotlinx.coroutines.CoroutineScopeKt.cancel(Lkotlinx/coroutines/CoroutineScope;Ljava/lang/String;Ljava/lang/Throwable;)V

which points to old version of coroutines lib being used. Sure enough by running gradle dependencies I see

kotlinCompilerPluginClasspath
\--- org.jetbrains.kotlin:kotlin-scripting-compiler-embeddable:1.3.61
...
     |    \--- org.jetbrains.kotlinx:kotlinx-coroutines-core:1.2.1

any ideaes on how to fix this?

[octylFractal]

https://docs.gradle.org/current/userguide/dependency_management.html#dependency-constraints

[Dariusz Kuc]

well so my build file is very simple

plugins {
    id("myPlugin")
}

dependencies {
    implementation("myLib")
}

[Dariusz Kuc]

and within those both myLib and myPlugin use proper coroutines version

[octylFractal]

that doesn't change the answer

[octylFractal]

it's still transitive dependency version management

[Dariusz Kuc]

sure but its coming from kotlinCompilerPluginClasspath

[Dariusz Kuc]

which i don't control

[octylFractal]

then how is it getting inside your dependencies

[octylFractal]

by that I mean the dependencies of your "custom task"

[octylFractal]

not the project dependencies in general

[Dariusz Kuc]

that is what i'm trying to figure out

[Dariusz Kuc]

old version of coroutines is pulled by compiler plugin classpath

[Dariusz Kuc]

e.g. runtimeClasspath and compile/default dependencies for projects are correct

[octylFractal]

you might just have to force it for that configuration then

[Dariusz Kuc]

wondering if i'm missing some configuration on my plugin

[Dariusz Kuc]

anyway thanks will look more into that tomorrow

[Dariusz Kuc]

ttyl