Not that I know of. publishing the kotlin artifac...
# multiplatform
p
Not that I know of. publishing the kotlin artifacts to Maven is pretty straight forward and works with the maven-publish plugin. A good example is Multiplatform-settings or Sql-delight. Should be able to c/p and change the relavent parts. As for publishing js to npm, I haven't seen any sort of integration with KMP. I imagine there is a gradle plugin for that but I have not looked into it.
r
Currently Multiplatform Settings is publishing with an undocumented modified Bintray plugin that Jetbrains put out for their early multiplatform libraries. I've been meaning to update that at some point since SqlDelight and other recent things publish with more stable configurations, but I haven't had time to dig into it yet.
Relatedly, I'd like to be publishing to Maven Central instead of just Bintray
p
oh, sorry, I looked at yours and thought it was the same. I must have used what SqlDelight is using
reduxkotlin.org also is an example
several libs there that publish to maven central
r
yeah there's plenty of stuff out there I just haven't had the time recently to dig in
k
Stately’s also maven central. It was originally the forked bintray thing, but I moved. Getting started with maven central takes more work as you have to essentially apply for the namespace, but it’s not bad, and once that’s done you’re all set. https://github.com/touchlab/Stately
The setup is copied from sqldelight, mostly
I have another project that also publishes an aar with multiplatform and gradle metadata, but it’s not public code yet. aar artifacts have traditionally been a little more complex.
Somebody does have a blog post explaining the bintray process for multiplatform in detail, but I don’t have the like. I know that’s not a super helpful comment, but it exists 🙂
r
Reminds me of an old joke about a mathematician who wakes up to a fire alarm, sees a fire extinguisher, says "a solution exists!" and then goes back to sleep.
k
Fair, but knowing there’s a blog post out there explaining it might just sustain the search effort vs not knowing it exists! Not for me, of course. I don’t need the blog post…