What is it that every second Kotlin release breaks...

# gradle

[Marc Knaup]

What is it that every second Kotlin release breaks publishing for me? 😞
I can build a multiplatform project just fine with build. But when I publish I get “Unresolved references” for subproject dependencies.

Anyone else having that and knows a workaround?

[Marc Knaup]

Looks like publishing is not or no longer compatible with org.gradle.parallel=true 🙄

[Dariusz Kuc]

might be related to this -> https://github.com/gradle/gradle/issues/15893

[Dariusz Kuc]

*if you are using mavenLocal in your build file

[Marc Knaup]

Thanks. I’ve uncommented mavenLocal() in my project. Same issue though 😕
Also, the problematic dependency is part of the same project to be published. It’s just another subproject.

[Dariusz Kuc]

it might be still the same issue -> Gradle might not be able to resolve module metadata for multiplatform module that was just published to maven local

[Marc Knaup]

It tries to resolve artifacts it has just created? That would be odd 😮

[Dariusz Kuc]

indeed, no idea though

[Javier]

@Marc Knaup do you have a jvm only module and a Multiplatform module with android?

[Marc Knaup]

no android

there are some jvm only modules involved though