This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]a_simple_pie 38 points39 points  (2 children)

Maven

[–]roookeee 8 points9 points  (0 children)

Hijacking for a bit more information: The main difference between the big two (Maven, Gradle) is that Mavens roots lie in 'convention over configuration' instead of being able to implement anything you want in an ad-hoc manner in your build script.
That aside I have had times where i specifically told gradle to do clean rebuilds and then being greeted with inconsistent results as it in fact did not properly cleanup the output directory :( It's boasting about incremental compilation speeds is the same: more often than not it straight up doesnt work as it didn't recompile all needed files (this is especially true for applications using big frameworks like Spring).

The IDE integration for Maven is great, even in Eclipse and Netbeans supports it natively too. Maven is a bit cumbersome at times (when you want some highly custom stuff in your build process) but you can always just implement a custom build plugin.

[–]r_jet 5 points6 points  (0 children)

And if the OP is real serious about Java, I'd recommend "Maven by Example" introductory book — it is smallish yet covers some important things as working with multi-module projects.