Quick question: why are some androidx artifacts fo...

# multiplatform

[Nathan Fallet]

Quick question: why are some androidx artifacts for Kotlin multiplatform directly available under the group id androidx.xxx while others are on org.jetbrains.androidx.xxx?

Is this something temporary until google merges multiplatform support? Or are they totally different libs?

[Nathan Fallet]

Example from dependencies of the Kotlin Conf app:

androidx-activity-compose = { module = "androidx.activity:activity-compose", version.ref = "androidx-activityCompose" }
androidx-core-ktx = { module = "androidx.core:core-ktx", version.ref = "androidx-core-ktx" }
androidx-core-splashscreen = { module = "androidx.core:core-splashscreen", version.ref = "androidx-core-splashscreen" }
androidx-espresso-core = { module = "androidx.test.espresso:espresso-core", version.ref = "androidx-espresso-core" }
androidx-navigation-compose = { module = "org.jetbrains.androidx.navigation:navigation-compose", version.ref = "androidx-navigation" }
androidx-lifecycle-runtime-compose = { module = "org.jetbrains.androidx.lifecycle:lifecycle-runtime-compose", version.ref = "androidx-lifecycle" }
androidx-lifecycle-viewmodel-compose = { module = "org.jetbrains.androidx.lifecycle:lifecycle-viewmodel-compose", version.ref = "androidx-lifecycle" }

[jw]

Temporary

[jw]

JetBrains led the multiplatform effort and Google moves really slowly