BTW, when I asked to include it to jcenter, got message: ``` Request to include the package '/msink/...

# kotlin-native

[msink]

BTW, when I asked to include it to jcenter, got message:

Request to include the package '/msink/kotlin-native/libui' in 'jcenter'

Hi, 

We can only approve one path for a single package.
Please let us know which path prefix you would like to include.

Thanks, 
JFrog Support

Yes, it is multiplatform package, really 3 separate packages for Linux/Windows/Mac...
Don't know what they want from me.

[elect]

you may want consider jitpack to avoid all this shits

[msink]

Well, it works on bintray, so will live here for a while.

[kpgalligan]

You can definitely publish multiple targets on both bintray and maven central. Config isn't necessarily "easy", but it's doable. I wouldn't come right out and say don't use jitpack, but if you want to share libraries and have people comfortably use them, don't use jitpack. Also, AFAIK, jitpack doesn't handle native.

[kpgalligan]

Example of multiple targets https://search.maven.org/search?q=stately

[kpgalligan]

I got bounced trying to publish to jcenter from bintray, but it was because a sources jar was missing from something. I've since abandoned that and copied from Alec/Jake and started publishing to sonatype/maven central. https://github.com/square/sqldelight

[kpgalligan]

However, if sticking to bintray, I hacked the JB hack to get metadata published to bintray, but to support gradle 4.10, if useful: https://github.com/touchlab/gradle-bintray-plugin

[msink]

I prefer to follow JB core infrastructure libs like coroutines and serialization. So in my case better stick to gradle 4.7 for now.

[kpgalligan]

Yeah, tough situation today. Newer android (3.3) requires 4.10, so straddling that world.

[msink]

Well, finally got

Your request to include your package /msink/kotlin-native/libui in Bintray's JCenter has been approved.

So now it works from jcenter()