<@U0BN58B38> when can we expect another Koma release? Really would like to start using the API chang...

# datascience

[thomasnield]

@kyonifer when can we expect another Koma release? Really would like to start using the API changes as a formal dependency....

[kyonifer]

@thomasnield i'm actually working on that currently. i've switched to new-mpp and am trying to use the experimental gradle metadata to allow native artifacts to be selected by their platform, as recommended by the native team. I'm still having some issues getting new-mpp to generate importable maven artifacts for native.

[kyonifer]

you can see my latest progress here: https://github.com/kyonifer/koma/tree/publishing I'm close though I think, so you can expect something soon

[orangy]

I’ve made a sample mpp project with publishing here: https://github.com/orangy/multiplatform-lib

[kyonifer]

@orangy yep and it was quite helpful, thanks! I saw it in your original #multiplatform post and based my solution off of it. I've got your publishing.gradle at https://github.com/kyonifer/koma/blob/publishing/buildscripts/publishing.gradle

[kyonifer]

i had to modify the artifact naming in publishing.gradle a bit to make it work with koma's multiple-artifacts-per-platform and im still having issues with segfaults importing the .klib's from the macX64 targets

[kyonifer]

it took awhile but i finally figured out how to get the module metadata to show all the available targets (even ones not buildable on this machine) and still keep code completion working

[kyonifer]

the answer to that was the workaround in https://github.com/JetBrains/kotlin-native/issues/2372. It might be useful for others if something along those lines made it back into the orangy/multiplatform-lib sample project

[orangy]

how about a PR? 🙂

[orangy]

there are some changes coming from inside from another project, but some time later

[kyonifer]

i can PR if it'll be awhile until another solution is available. just add two native targets and then expose a publishing property sound good?

[orangy]

I’m somewhat tired, so didn’t yet got deep into the problem. Will check it tomorrow.

[kyonifer]

@thomasnield I've pushed up a 0.13-RC1. To use various workarounds I had to depend on the kotlin EAP so its not ready to be released yet. When kotlin 1.3.20 is released koma should as well.

[kyonifer]

@orangy one other mod i had to do to publishing.gradle: remove it.name != 'kotlinMultiplatform' from the bintrayUpload.doFirst task. I have projects A and B and project A depends on B, and the pom that gets generated for A looks for the generic kotlinMultiplatform project of B which didnt exist because it was excluded there. Publishing all the projects to bintray solved the issue. Is there a reason for excluding it from bintray?

[kyonifer]

in particular project A had this in its pom:

<dependency>
      <groupId>com.kyonifer</groupId>
      <artifactId>koma-core-api</artifactId>
      <version>0.13-RC1</version>
      <scope>runtime</scope>
    </dependency>

[kyonifer]

where koma-core-api is the real name of project B 🙂

[thomasnield]

@kyonifer thanks!