-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish maven artifact #13
Comments
Sure, but I think this should wait for Kotlin 1.3.10 or maybe even 1.3.20. Now it is a bit rough on edges. |
Well, in Kotlin 1.3.10 some bugs we're fixed, https://youtrack.jetbrains.com/issue/KT-27803 So now publishing to bintray should work, with some tricks - Gradle must be 4.7 (it is), But I have very little free time this week for experiments, so if interested - go on :) |
Published, should work like this:
Still didn't figure out how to publish it as true multiplatform library, for using as
|
Asked JetBrains developers: JetBrains/kotlin-native#2372 |
Well, issue with multiplatform library resolved, so this almost works. See template project https://github.com/msink/hello-libui On Linux and on MacOSX it should work already, on Windows - only if you have built something by Kotlin/Native on this computer, on Appveyor it fails. |
And before it will be published to jcenter or mavenCentral - what version numbering scheme should be used? I'm not sure. |
Good news with the publishing! Just to share some thoughts for the numbering scheme: Imo you should not align it to the libui version, because you might want to do changes, while the libui version remains the same, and vice versa. It should probably be alpha, as long as libui is. So maybe something like 0.1.0 (at least this is what the semver FAQ suggests to start with). My laptop works again (I broke it during the vacation), so I'm eager to check your changes. |
For the windows issue: Maybe the dependsOn is the problem: We can find out which task downloads |
I tried - seems that there isn't such gradle task. |
Done. |
And to |
So new projects can just use kotlin-libui as a normal dependency
See #7
The text was updated successfully, but these errors were encountered: