Does anyone know if it's possible for multiplatfor...

# library-development

[Emil Kantis]

Does anyone know if it's possible for multiplatform libraries to work w/ maven without requiring users to explicitly depend on the -jvm artifact? It seems to me that both Arrow and Kotlinx.serialization have somehow resolved this.

[Adam S]

Kotlinx Serialization achieves this by editing the POM for the unflavoured module https://github.com/Kotlin/kotlinx.serialization/blob/1116f5f13a957feecda47d5e08b0aa335fc010fa/gradle/publish-mpp-root-module-in-platform.gradle#L6-L45

[Adam S]

and it looks like Arrow does the same https://github.com/arrow-kt/arrow-gradle-config/blob/0.12.0-rc.20/arrow-gradle-config-publish/src/main/kotlin/internal/PublishMppRootModuleInPlatform.kt

[Emil Kantis]

Thanks Adam! I'll check if we can apply that in Kotest too.

If anyone from JB stumbles upon this, would it make sense to make this the default behaviour when packaging multiplatform publications? It seems to be an annoying gotcha that Maven users always stumble into when using multiplatform libraries.. See https://github.com/kotest/kotest/pull/3858

[Adam S]

I have a vague memory that the reason that Coroutines and Serialization have this hack is because they predate the -jvm suffix convention, and so they retained it to maintain backwards compatibility when the -jvm suffix was introduced. Adding the -jvm suffix is the planned default for Maven-based resolution

[Adam S]

personally I'd rather tell all non-Gradle users to use -jvm than risk hacking around with Gradle 🙃

[Emil Kantis]

Then I think it would make sense to add a section regarding multiplatform dependencies on https://kotlinlang.org/docs/maven.html 🙂

[Emil Kantis]

Either way I sort of like the rewrite hack.. It makes sense not to surprise users, and it is kinda hard to tell if a library is JVM-only or multiplatform at first glance.

[Adam S]

good idea for a YouTrack issue :) https://kotl.in/issue

[Adam S]

and yeah it's pretty clever

[Adam S]

and it helps out Kotlin scripting too, because it uses Maven coordinates

[Adam S]

apparently the Gradle artifact resolution logic is too embedded and can't be split out to be used standalone, which is a shame

[Emil Kantis]

Published a YT issue

[mbonnin]

I opened that one some time ago. Would be really nice to have