Is there anything unusual with the publication of ...
# coroutines
c
Is there anything unusual with the publication of coroutines 1.7.2 and consumption by multiplatform projects? I’m bumping from 1.7.1 to 1.7.2 and consistently get the error below across multiple independent Kotlin multiplatform projects. I can see the artifact exists, because I can follow the URL and the JAR is there. When I build an non multiplatform Android project, everything works as expected.
Copy code
* What went wrong:
Execution failed for task ':io-lib:compileKotlinJvm'.
> Could not resolve all files for configuration ':io-lib:jvmCompileClasspath'.
   > Could not find kotlinx-coroutines-core-jvm-1.7.2.jar (org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm:1.7.2).
     Searched in the following locations:
         <https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/kotlinx-coroutines-core-jvm/1.7.2/kotlinx-coroutines-core-jvm-1.7.2.jar>
d
Is there anything unusual with the publication of coroutines 1.7.2 and consumption by multiplatform projects?
99% sure there isn't. The person who published the release has been on vacation since today's morning, so I can't say for sure, but we have an established release procedure that we follow each time, and I haven't heard of any deviations happening this time.
c
Is there anything in particular that would be helpful to troubleshoot this further? I’m using Kotlin 1.8.22, Gradle 8.1.1, macOS. I can try for a smaller repro case, although that may take some time.
d
We can all see the link works, so I have no clue what's going on on your end. Maybe restart your computer? Or
pkill java
? For example, in a case when Gradle's daemon works in the background and thinks it doesn't need to check the link again, or something like that.
c
So it works on a different computer 🤦. Let me try rebooting this one.
c
The upgrade worked for me on https://gitlab.com/opensavvy/pedestal, so I don't think the issue is with the library itself
c
Yeah, I also got it to work after a reboot. What a strange issue. I’ve never had a Gradle build fail in that particular way before.
Thanks for the help Dmitry and Ian.