3 ms·
I used to use Maven but I've moved completely to Gradle. With Maven, if you follow Maven's way of doing things, everything just works. But, if you need to do s
by skissane 9y ago
I used to use Maven but I've moved completely to Gradle.
With Maven, if you follow Maven's way of doing things, everything just works. But, if you need to do something different, or have some rare use case Maven's designers weren't focused on, you start struggling a lot to get Maven to do what you want.
Gradle is a lot more flexible and if you have some uncommon requirement you are far more likely to successfully implement it using Gradle than using Maven.
- lmm 9y ago> But, if you need to do something different, or have some rare use case Maven's designers weren't focused on, you start struggling a lot to get Maven to do what you want. You'll be fine as long as you realise the Maven-ey way of doing the thing is to write your own plugin. But most of the time people just want their build to do something different for no real reason, IME.
- andrewaylett 9y agoOne time I got frustrated enough with Maven not quite supporting what I wanted to do that I sat down and wrote a plugin that just did what I needed. A short while later I was wondering why I'd never tried that before: Maven plugins are really quite simple to write.