Is there a up-to-date resource that I can read regarding publishing a MPP library? I only get as far...

# multiplatform

[Hauke Radtki]

Is there a up-to-date resource that I can read regarding publishing a MPP library? I only get as far as publishing to mavenLocal

[Hauke Radtki]

Especially when using the multiplatform plugin (and not the old method (kotlin-platform-{common,native,jvm}))

[orangy]

I’ve made a sample some time ago with tests and publishing in MPP https://github.com/orangy/multiplatform-lib

[Hauke Radtki]

Thanks 👍

[Hauke Radtki]

Did you test that with an android target (i.e. from presets.android)? For me the info is missing in the gradle metadata (other targets are correct though)

[orangy]

No, I didn’t, but should be same as JVM?

[Hauke Radtki]

I'm pretty confident that it is not an issue of your example (which was really helpful!) but with the way the multiplatform gradle plugin creates the publications.
Do you have an idea where I can look for a workaround?

[orangy]

Can you provide more detailed description of what’s not working? May be @h0tk3y can suggest a workaround or solution.

[Hauke Radtki]

Sure, I will put together a minimal example. But in the meantime:
I test this with publishToMavenLocal, it generates folders for all variants (I use iOS, Android and now JVM for additional testing) plus a folder for metadata.

Layout:
com.example
--> lib
--> lib-android
--> lib-jvm
--> lib-iOS
--> lib-metadata

lib-android contains no artifacts. And if I force it to contain the librarie's aars, they are not recognized. I guess because the metadata (i figure the *.module file contains it) does not have any information about the actual files

[Hauke Radtki]

https://github.com/HaukeRa/KotlinMultiplatformTest/tree/metadata

checkout --> "gradlew build publishToMavenLocal" --> inspect contents of %HOME%/.m2/com.example folder

[h0tk3y]

@Hauke Radtki Publishing of Android targets was not yet implemented in 1.3.11 (https://youtrack.jetbrains.com/issue/KT-27535). This feature will be available in 1.3.20 (you will be able to try it in the upcoming 1.3.20 EAP-3, though not in the previous EAPs).

[Hauke Radtki]

Ah, thanks for the info. Somehow my search did not bring up this issue. I will give it a try!

[Hauke Radtki]

@h0tk3y 1.3.20-eap-100 (which should be EAP-3, correct?) doesn't generate anything for android, is further configuration needed?

[h0tk3y]

@Hauke Radtki 1.3.20-eap-100 is currently under testing, we will likely announce it as the EAP 3 or deploy a new build if we find any issues with that one. Yes, it requires additional configuration for publishing Android libraries. You need to choose which variants to publish, none are published by default in this version. It is done as follows if you only want to publish the release variant:

kotlin {
    android { // configure the Android target
        publishLibraryVariants("release")
    }
}

I'll post more details in the #multiplatform channel once we announce the EAP 3.

[Hauke Radtki]

Works as expected. You saved my day 😎

[orangy]

@h0tk3y EAP 3 was already announced: https://kotlinlang.slack.com/archives/C0KLZSCHF/p1547583471006700

[h0tk3y]

Ah, OK, thanks.

[h0tk3y]

Here are the details: https://kotlinlang.slack.com/archives/C3PQML5NU/p1547634772240200