Anonymous
Unregistered
|
|
Nice article. Although Maven2 is maturing, it still has a somewhat unfinished feel to it and the bundled plugins are lagging behind. It also lacks some features such as aggregating sites in multiproject builds. Documentation is poor, inconsistent and incorrect in some places. A recommended read is the excellent "Better builds with Maven" from Mergere (http://www.mergere.com/m2book_download.jsp) which helps a lot to say the least. The concept with Maven is however great and once you get all plugins (bundled and external) working your way you will be happy - guaranteed. 
|
Anonymous
Unregistered
|
|
Maven is necessary for J2EE project due to their inherent complexity. I'm sure M2 will eventually be a footnote in history, but a significant one, as we work our way to unifying and consolidating modern project structures, in the same way that OO consolidated structured programming failures.... of course, you could always just use Rails!
|
Unregistered
|
|
Rails... *pukes*
|
Unregistered
|
|
You have to be kidding when you say that Maven is necessary for J2EE projects! We have sophisticated J2EE projects that use Ant for build maintenance.
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
