Support for Maven had always low priority

# announcements

[cy]

Support for Maven had always low priority

[poohbar]

That's a terrible idea tbh.

[poohbar]

Who unanimously decided that Gradle is the way to go? Have you ever had to maintain huge projects in Gradle? It's a major PITA.

[cy]

Nobody particularly, just the world goes to Gradle

[poohbar]

Just check the IntelliJ stats you collect about how many projects use Maven vs Gradle and you will find how wrong you are.

[cy]

There is also delta: a lot of projects migrating to Gradle

[poohbar]

Gradle with dying deprecated Groovy as a first class build-language and buggy Kotlin-build-language support. What a marvellous idea.

[cy]

And almost none migrating back from Gradle to Maven

[Czar]

I sense a holywar brewing 😄

[Czar]

https://stackshare.io/stackups/gradle-vs-jitpack-vs-maven

[poohbar]

I am not trying to start a flame war but I believe Maven should absolutely get as much support as Gradle does and anything else is a huge mistake and a huge middle finger to thousands of devs on Maven.

[poohbar]

You could be opinionated about this if Kotlin's adoption was skyrocketing. But is it really?

[poohbar]

It was so hard to convince my team to start using Kotlin and now you are trying to tell me we should switch to Gradle as well. That's not happening. So I might eventually be stuck with a project that does not even build!

[cy]

There is nothing about actual advantages/disadvantages of Gradle, it's just about fashion, hype

[cy]

today it's quite popular and it's popularity is growing, also it is almost the only build tool for Android

[poohbar]

Sure, but we can't just migrate the huge project to Gradle. You have to support both. God damn you support Java 1.6!

[Shawn]

dude who pissed in your cheerios this morning

[poohbar]

this guy ^

[Shawn]

nobody’s saying anything about abandoning maven entirely

[Shawn]

all sergey said was that maven support has been low priority, and for relatively sound reasons

[poohbar]

lol sound reasons

[poohbar]

giving into the hype and fashion is a sound reason..

[Shawn]

JetBrains makes tools for other people

[Shawn]

they’re not going to prescribe a build tool to the whole of the Android community

[cy]

you known, incremental compilation support has been added to the maven plugin much much later

[Shawn]

if the vast majority of the Android community uses gradle, JB’s not going to “give them the middle finger” and tell them they’re not going to prioritize gradle

[poohbar]

Wait I am not saying to prescribe anything. Both Maven and Gradle are widely used and I believe Maven is even more prevalent than Gradle. If not it might be around 1:1. So what's the reason to support one less? Makes no sense.

[Shawn]

I’m going to hazard a guess and say Gradle is far more commonly used in both Android and Kotlin development overall.

[Shawn]

You really only need to idle on this slack for a few days to tell most the build tool related questions are gradle ones

[poohbar]

Yeah because Gradle is incomprehensible so people have to ask about everything.

[Shawn]

and if you’re gonna complain about other people mischaracterizing your arguments, maybe stop mischaracterizing other peoples

[Shawn]

Are you intentionally doing this?

[cy]

so, finally the only we can do for now is to vote for the issue and wait

[cy]

Also note that there are workarounds

[poohbar]

Why would it work with 1.2.10 though?

[cy]

Regression, probably caused by Java-Kotlin interop IC improvements

[poohbar]

I guess experimental means truly experimental in this phase. As long as everything else works it's fine.

[cy]

as I noted in the issue, you can simply add extra copy-resources execution after kotlin plugin to get resources back (compiler simply removes copied resources)

[poohbar]

thanks

[poohbar]

sound reasons:

https://trends.google.com/trends/explore?date=all&q=gradle,maven

[Shawn]

ooh, I can make graphs too

[Shawn]

https://trends.google.com/trends/explore?date=all&q=gradle%20android,maven%20android