theapache64
03/02/2025, 1:00 AMtheapache64
03/02/2025, 1:01 AMtheapache64
03/02/2025, 1:02 AMtheapache64
03/02/2025, 1:05 AMtheapache64
03/02/2025, 1:07 AMjoffrey
03/02/2025, 1:08 AMWhich one is more preferred, given that I am targetting to work with Compose Multiplatform projectThe Gradle-based Amper plugin was meant for us to quickly gather feedback about Amper, but we're mostly focused on the standalone Amper now. This is definitely preferred. So please use standalone Amper unless you're lacking some critical feature (and if you do, please open an issue and let us know in this channel 🙏🏻)
Second question, I am planning to build a Compose Multiplatform library and I assume the publishing part (to things like mavenCentral, jitpack) works without any extra tricksAmper standalone cannot publish KMP libraries yet, only single-platform JVM libraries. With Gradle-based Amper, you should be able to publish KMP libraries, but it doesn't have all the maven central publication built-in, though. So you still have to configure maven central stuff in your Gradle build files like you would in "pure" Gradle. We definitely aim at providing a much better out-of-the-box experience for publishing libraries in standalone Amper, but we didn't have the resources to focus on that just yet. We are now going to work on this, please stay tuned! 😉
joffrey
03/02/2025, 1:08 AMtheapache64
03/02/2025, 1:10 AMtheapache64
03/02/2025, 1:11 AMtheapache64
03/02/2025, 1:11 AMjoffrey
03/02/2025, 1:17 AM