I think it depends on your experience and/or skills. I wouldn't pick Maven anymore for something new; you need acres of XML to (almost) achieve anything with it.
On the other hand, it's widely supported ― although I haven't hit a dead-end with Gradle...yet.
08/27/2017, 12:57 AM
You can’t go wrong with either. Maven is still the undisputed champ in the Java dependency management/build tool world. I love gradle, it’s more intuitive and cleaner. It uses the maven central repos and allows for groovy instead of xml in the build file. Android uses gradle and Spring is a huge proponent too.
08/27/2017, 7:37 AM
Maven is proven and is hard to get wrong.
Gradle is more powerful but with great powers come great responsibility.
(Disclaimer: I hate Gradle)
08/27/2017, 8:25 AM
I used Maven for many years, then switched to Gradle for a year and went back to Maven. In the projects I do, I've needed the extra functionality that Gradle brings to the table. Maven's XML might be verbose, but reading through it, you can see exactly what you're looking at.
08/27/2017, 11:13 AM
oops … I started before I got all these replies and chose gradle … I’ll go back over your recommendations though and maybe do maven too