kotlinx-coroutines-bom seems to break upgrade to Spring Boot 2.7.1

Hi there, I’m not sure if I should open the issue here too but I noticed that after trying to upgrade to Spring boot 2.7.1 I’m getting this error:

[ERROR] Failed to execute goal on project stamps-and-coins-service: 
Could not resolve dependencies for project 
org.jesperancinha.enterprise:stamps-and-coins-service:jar:0.0.1-SNAPSHOT: org.jetbrains.kotlinx:kotlinx-coroutines-bom:jar:1.6.3 was not found in 
https://repo.maven.apache.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]

I dug into the BOM of spring boot and I found that it is using kotlinx-coroutines-bom 1.6.3 which is using kotlinx-coroutines-debug dependency which wants to download apparently a BOM as a jar file:

    <dependency>
      <groupId>org.jetbrains.kotlinx</groupId>
      <artifactId>kotlinx-coroutines-bom</artifactId>
      <version>1.6.3</version>
      <scope>runtime</scope>
    </dependency>

Have you seen this issue and are you going to release a fix soon?

Thanks!

[wilkinsona]

Thanks, @jesperancinha. We import kotlinx-coroutines-bom into our spring-boot-dependencies bom. In 2.7.1 we’ve upgraded from 1.6.1 to 1.6.3 which means that any dependency on the debug library now uses a version with a faulty pom. This didn’t affect Boot’s build as we do not depend, directly or transitively, on kotlinx-coroutines-debug. You can work around the problem by setting kotlin-coroutines.version to 1.6.1.

Given that the problem is limited to users kotlinx-coroutines-debug and that there is a workaround, we’ll leave things as they are in Spring Boot. We’ll pick up 1.6.4 when it’s released which should address the problem at source.

[jesperancinha]

I think I found out what’s needing that debug library.

        <dependency>
            <groupId>io.kotest</groupId>
            <artifactId>kotest-runner-junit5-jvm</artifactId>
            <scope>test</scope>
        </dependency>

Tough one this one 😃 because then it will only happen to whoever is using Kotest, but apparently this one actually starts in kotlinx coroutines, that’s where the problem seems to begin. I’m waiting for a reaction from them at the moment, but this seems to be an issue with the kotlinx-couroutines libraries.