in order to provide support for KMP artifacts from maven. Currently we are having issues in Arrow and wondering if this is needed or if there is a better way to solve it. Thanks!
Jilles van Gurp
8 months ago
I think the status with maven is that you are pretty much on your own. It's very much a second class citizen in the Kotlin ecosystem at this point. That means relatively few users, documentation that lags behind, harder to get support, and all sorts of things you can easily do in Gradle with it's kotlin scripting support that just flat out won't work in maven or would work completely differently.