Identical naming of compose.components.* jars breaks packaging with Conveyor

[iamcalledrob]

Describe the bug compose.components.resources and compose.components.uiToolingPreview both generate a jar named library-desktop-1.6.0.jar

Depending on both, along the lines of:

kotlin {
    jvmToolchain(17)
    jvm("desktop")

    sourceSets {
        val desktopMain by getting
        desktopMain.dependencies {
            implementation(compose.desktop.currentOs)

            implementation(compose.components.resources) // <--
            implementation(compose.components.uiToolingPreview) // <--
        }
    }
}

will generate two identically named jars, which breaks packaging with Conveyor -- the second jar to be ingested will overwrite the first, leading to java.lang.NoClassDefFoundError: org/jetbrains/compose/resources/DrawableResource at runtime.

Having duplicate jar names will also make stack traces less useful.

This may not technically be a bug, but it feels like an oversight.

Affected platforms

• Desktop (Windows, Linux, macOS)

Versions

• Kotlin version*:
• Compose Multiplatform version*: 1.6.0
• OS version(s)* (required for Desktop and iOS issues): Windows 11
• OS architecture (x86 or arm64): x86
• JDK (for desktop issues): Temurin 21

To Reproduce Make a compose desktop project, and add both dependencies.

Expected behavior The jars generated are named differently.

Screenshots Packaging with the built-in packager works only because of the hash appended to the jar name.

Additional context

[okushnikov]

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.