While publishing an Android library from my KMM li...

# multiplatform

[shahroz]

While publishing an Android library from my KMM library, i am facing something very weird, I am probably missing a step in the middle

If my build.gradle file doesn't have an artifact-id the library that gets published works fine.

Without artifactId

group = "io.data.shared"
version = "1.0"

my content of my maven repo looks like this (which is fine):

5206 Oct 27 21:42 shared-android-1.0-sources.jar
10971 Oct 27 21:42 shared-android-1.0.aar
8813 Oct 27 21:42 shared-android-1.0.module
6831 Oct 27 21:42 shared-android-1.0.pom

With artifact Id

publishing {
    publications {
        create<MavenPublication>("maven") {
            groupId = "io.data.android"
            artifactId = "shared"
            version = "1.0.0"
        }
    }
}

my content of my maven repo looks like this (which isn't android specific):

shared-1.0.0-kotlin-tooling-metadata.json
shared-1.0.0-sources.jar
shared-1.0.0.jar
shared-1.0.0.module
shared-1.0.0.pom

[Jeff Lockhart]

Are you specifying the library variants to publish?

kotlin {
    android {
        publishAllLibraryVariants()
        // or e.g.
publishLibraryVariants("release")
    }
}

[Trey]

Is there a way to specify the artifact name for each publication? My project is using the name of the module, but I want a shorter name without camelCase.

[Jeff Lockhart]

I've only used the module name as the artifact name. I recall experiencing issues configuring the name manually, so I settled on naming the module for the artifact. I just recall Android having the additional requirement of publishing variants and wasn't sure if that might be a difference in your config.

[shahroz]

yup, added the additional requirement for android

kotlin {
    android {
        publishLibraryVariants("release", "debug")
    }
}