I like maven. There, I said it. Now where is my flame suit?
Last night at the Nashville Java User Group meeting, Kerry gave a good introductory presentation on maven. He talked about the pros and cons, and showed some things like phases, profiles, and parent/child projects. For those who had little to no experience with maven, it was a good introduction. Hopefully they will read more.
I jested afterwards that he should write a blog entry to generate traffic for his web site, because a discussion about maven is never luke warm. People come out either strongly for it or against it. I expressed this at last night’s meeting. Well, sitting here this morning and checking twitter, etc., I realized that I would be a bit of hypocrite if I wasn’t willing to put my money where my mouth was and write my own blog entry.
So here we go. I like maven for a handful of reasons:
- consistent format of project layout
- transitive dependency management
- more plugins than I can imagine
- declarative definition that supports convention over configuration
- maven’s one-artifact-per-project promotes a better breakout of modules