josephivie
02/09/2019, 6:29 PMaddamsson
02/09/2019, 6:29 PMjosephivie
02/09/2019, 6:30 PMaddamsson
02/09/2019, 6:30 PMjosephivie
02/09/2019, 6:31 PMaddamsson
02/09/2019, 6:31 PMkotlin-multiplatform
pluginjosephivie
02/09/2019, 6:32 PMKonvenience
, 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 {}
}
}
addamsson
02/09/2019, 6:36 PMKonvenience
?ian.shaun.thomas
02/09/2019, 6:37 PMaddamsson
02/09/2019, 6:37 PMian.shaun.thomas
02/09/2019, 6:37 PMaddamsson
02/09/2019, 6:38 PMjosephivie
02/09/2019, 6:44 PMaddamsson
02/09/2019, 6:47 PMkpgalligan
02/09/2019, 8:53 PMjosephivie
02/10/2019, 12:04 AMPOM.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.