That said, it's still better than anything else I know of at its job. I just wish they would have had Kotlin when they started.

let's move this to a thread

Agreed

(in beta / experimental)

I know it will be. It's just frustrating to see how short of its potential it is now that we can use Kotlin but most of the APIs are still untyped.

indeed

Agreed. Thankfully, by making a plugin I'm calling

Konvenience

, I got the main part of my file down to this:

kotlin {
    all()

    sources {
        main {
            mpp(standardLibrary)
        }
        test {
            mpp(testing)
            mpp(testingAnnotations)
//            mpp(mavenDashPlatform("com.lightningkite", "kommon", "0.0.2"))
        }
        isNonNative.sources {
            isJvm.sources {}
            isJs.sources {}
        }
        isNative.sources {}
    }
}

what's

Konvenience

?

that's the name of the plugin he's making (apparently).

oh, sorry

I had to read it twice as well

I'm a bit preoccupied, my bad 😞

That's correct. It will be released sometime today unless something goes horribly wrong.

👍

Maven central deployment? There are multiple examples of how this all works together now. Native is more complex because it uses metadata, which means you need to have the right versions of gradle, but it works.

@kpgalligan It's a collection of convenience functions for multiplatform projects. For example, there's a quick way to add information to the POMs of every artifact. There's a

POM.github(url)

which specifies VCS/Issue URL/Website all at once. There's a system for defining target platforms based on what dependencies you have, and specifying dependencies in a format that ensures you catch unsatisfied dependencies earlier. You can also define source sets and the relations between them in a hierarchical manner very quickly. There's a

dokka()

function which invokes dokka on your project and attaches the output to all of the publications.