Arkadii Ivanov11/29/2020, 3:07 PM
requires Kotlin 1.4.20, whereas Jetpack Compose
requires Kotlin 1.4.10. Looks like I'm forced to use some older version of JetBrains Compose.
jim11/29/2020, 3:11 PM
Arkadii Ivanov11/29/2020, 3:14 PM
modules. Each uses the corresponding Compose variant. The former is pure Android library, the latter is multiplatform.
jim11/29/2020, 3:17 PM
Javier11/29/2020, 3:19 PM
if there are specific APIs only for Android, then that implementation in
add them without having to add the Google one, like a normal MPP library? @jim
Arkadii Ivanov11/29/2020, 3:19 PM
jim11/29/2020, 3:20 PM
needed to be compatible with a published alpha release of Compose on gmaven. If the concern is just being able to access android-specific APIs, then yes, just use
Arkadii Ivanov11/29/2020, 3:25 PM
to 1.0.0-alpha07, and
to 0.2.0-build132. It does not compile
jim11/29/2020, 3:37 PM
) should compile with 1.4.20. The problem (as I understand it) is that you're trying to straddle both releases simultaneously for the purposes of providing your own releases that are compatible with both google+jetbrains latest releases, right?
Arkadii Ivanov11/29/2020, 3:45 PM
with dependency on JetBrains Compose. Because Jetpack and JetBrains Compose are different publications in different repositories, and are not binary compatible.
with Kotlin 1.4.10 + version
with Kotlin 1.4.20 but without
jim11/29/2020, 3:50 PM
with 1.4.20 for use in MPP-android projects. That is to say, you publish two variants of all your artifacts (one for MPP users, and one for gmaven/android-only users). I understand this is very not ideal, but should hopefully only be short term.
Arkadii Ivanov11/29/2020, 3:50 PM
Javier11/29/2020, 4:09 PM
Arkadii Ivanov11/29/2020, 4:11 PM
Andrey Kulikov11/29/2020, 6:19 PM