Considering creating a fork of coroutines just so that I can compile it with a later version of Gradle - it's currently on

4.10

which is generating an incompatibly old version of meta-data vs. say, `4.8`+ which I'm having to use to support Java 12. In the event, I can compile ok, but multi-platform modules which are dependent on coroutines fail when publishing their own metadata.

kotlinx.coroutines is using stable Gradle metadata since it's out in Gradle 5.3. That should be since version 1.2.1 of kotlinx.coroutines (but I use 1.3.0-RC2 with Kotlin 1.3.41). You should not need to fork it, but only update to Gradle 5.3 (or 5.5.1 or 5.6.0-rc-2+)

I'm encountering another bug then because by default I'm going latest with everything, and

5.5.1

and

5.6-RC2

were what I started out with. Metadata reads fine and platform targets all build but then the publish Metadata step fails citing it couldn't resolve coroutines 🤔.

@darkmoon_uk You probably forgot to add the dependency on

core-common

from kotlinx.coroutines

OMG it was that... @louiscad, you saved me from a dark place today 😅 .