That link needs one more vote. Make it yours! Login and vote now.
By gst
via esumerfield.blogspot.com
Published: Sep 24 2007 / 10:28
Every project I start I try to use Maven. It seems like the right choice but I consistently fail. Every step is hard. It's not just that there are infrastructure hurdles, but the commands are hard, the POM is complex and nothing is easy.
Comments
utakapp replied ago:
To set up a project with Maven is a real struggle. The original problem is not maven, but our complex open source world. Each project is built on a stack of other open source projects. Once the project it is set up well, it works fine. When you try to upgrade a version of a library you might be caught in new dependency troubles.
Craig Tataryn replied ago:
I can imagine Maven being a challenge for people not willing to invest time in learning it.
+1 for Maven, -1 for people who can't understand documentation: http://www.sonatype.com/book/index.html
If you want easy, grab a plugin for your IDE.
Chaucerian replied ago:
Maven is the "drunk girl in a relationship fight" of Java, you want to help but you know if you get involved she will turn on you.
mostlyharmless replied ago:
I think whines about maven are the number one pollutant of Dzone's front page.
My advice: Read the docs, follow a tutorial, make sure you reading about and using maven2, not maven1.
Chaucerian replied ago:
The YAGNI principle is just as relevant to tool selection.
Voters For This Link (13)
Voters Against This Link (0)