I ve not yet figured out how to get publishing to work other

Question

I ve not yet figured out how to get publishing to work other than through mavenLocal so if you want to try I recommend to wait a little unless you want to clone it and dig a bit

ribesg · Answer

I ve got this ``` publishing repositories maven url = if Versions isSnapshot uri snapshot repo uri else uri release repo uri credentials username = username password = password ```

ribesg · Answer

That s all I need with the maven publish plugin

ribesg · Answer

Then on the android target I call `publishAllLibraryVariants ` and my iOS targets are defined like this ``` for targetName presetName id in iosTargets targetFromPreset presets getByName lt KotlinNativeTargetPreset gt presetName targetName mavenPublication artifactId = $ project name $id ```

louiscad · Answer

I m using this to publish to bintray <https github com h0tk3y better parse blob fb2d5fb81b2a5eaccbe30419295f21ce1f70e5b0 build gradle L126>

louiscad · Answer

But now I m waiting <https kotlinlang slack com archives C3PQML5NU p1560769296185600 thread ts=1560607343 176700 amp cid=C3PQML5NU>

ribesg · Answer

Yeah I m publishing to a private artifactory instance it s pretty much instant

ribesg · Answer

Compared to the time it takes to build the iOS targets

louiscad · Answer

Oh yeah that is so slow I hope it ll improve before I add iOS support to too many splits On a more positive note that may encourage me to add a CI to the project so my laptop can stay cool

ribesg · Answer

Yeah a MacOS CI confused

louiscad · Answer

Travis CI does it as I saw it run checks on macOS last time I submitted a PR to SqlDelight

louiscad · Answer

Did you ever encounter such an error gt Variant android releaseApiElements capability com louiscad splitties splitties fun pack android base with views dsl 3 0 0 dev 015 gt Incompatible attribute gt Required com android build api attributes BuildTypeAttr debug and found incompatible value release

ribesg · Answer

Yes you need to publish both release and debug

ribesg · Answer

I did not find a way to say that release dependencies were fine to use with debug build

louiscad · Answer

But will these not overlap

ribesg · Answer

No one will be `lib android debug`

louiscad · Answer

And the other will have ` release` suffix

ribesg · Answer

No

louiscad · Answer

That means that I m breaking it by setting a custom `artifactId` in `mavenPublication `

ribesg · Answer

Maybe I m using this for the Android target ``` android publishAllLibraryVariants ```

louiscad · Answer

Oh found this by navigation from `publishAllLibraryVariants ` ``` if publishLibraryVariantsGroupedByFlavor defaultArtifactIdSuffix = dashSeparatedName getFlavorNames androidVariant + getBuildTypeName androidVariant takeIf it = release map it toLowerCase takeIf it isNotEmpty ```

louiscad · Answer

That explains

louiscad · Answer

I ve tried to add an option to skip the Kotlin Native targets but it s bringing an error when I activate it ``` What went wrong Could not determine the dependencies of task fun packs android base publishAndroidDebugPublicationToMavenLocal gt Publishing is not able to resolve a dependency on a project with multiple publications that have different coordinates Found the following publications in project modules bitflags Maven publication kotlinMultiplatform with coordinates com louiscad splitties splitties bitflags mpp 3 0 0 dev 015 Maven publication macosX64 with coordinates com louiscad splitties splitties bitflags macosx64 3 0 0 dev 015 Maven publication iosX64 with coordinates com louiscad splitties splitties bitflags iosx64 3 0 0 dev 015 Maven publication iosArm64 with coordinates com louiscad splitties splitties bitflags iosarm64 3 0 0 dev 015 Maven publication iosArm32 with coordinates com louiscad splitties splitties bitflags iosarm32 3 0 0 dev 015 ``` Have you ever encountered such a thing

ribesg · Answer

I tried once to build only the android targets to see if I could build them on a non MacOS CI and failed