For what it's worth, I like Maven 2.0. The show stopper for me as far as having my team switch to it is the insufficiency of the Eclipse plugin for Maven. We use Eclipse as our IDE, and a pom editor would be very nice, as well as a more full-functioned dependency search utility.
Also, we're mainly developing and running in JDK 1.5 now, and it seems that there are some problems there. I can't get a war package to run in Eclipse using the MNGECLIPSE plugin. -K On 1/19/06 4:15 PM, "Darren Hartford" <[EMAIL PROTECTED]> wrote: > I have been using since Maven pre-1.0, and actually have it in > production in a couple larger projects and have been happy with the > general documentation and maturity of the maven 1.0, 1.1 series. > > However, I am supporting Jeroen's perception of Maven 2.0's "features > are lacking or not-quite-there-yet" statement. Some of the great things > of Maven 1.0/1.1 that developers have switched to and rely on are not > available yet in Maven 2.0 -- and this may be more about the plugins > themselves rather than the Maven 2.0 core. I know there have been > discussions/threads regarding backward compatability for plugins that > may help the feature-list. > > And as for documentation, well, examples are worth a lot more than > several chapters of theory/reasoning/why-we-are-planning-ahead-this-way > documentation. The people on the mailing lists, both committers and the > user-base, have been very supportive regardless if there was > documentation related to the issue. :-) > > Keep Maven rolling! > > -D > > >> -----Original Message----- >> From: Peschier J. (Jeroen) [mailto:[EMAIL PROTECTED] >> Sent: Thursday, January 19, 2006 11:15 AM >> To: Maven Users List >> Subject: RE: Worst documentation in the whole apache projects >> >> >> Considering Maven is the work of volunteers I understand it >> comes with no kind of warranty as to the quality of the >> product or the documentation. However, since Maven is >> portrayed as an Apache project you certain expectations are raised. >> >> High profile open source projects like Maven should act >> responsibly instead of hiding behind the "no warranty" claim. >> Payroll developers using Maven for production work expect >> something to work. Some of the features Maven claim to have >> are, at best, unfinished. >> >> I have been evaluating Maven since 2.0 but we have not yet >> switched because features are lacking or not-quite-there-yet. >> Development on Maven seems active so I am optimistic about it >> maturing to a level to be used in production environments. >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Kathryn Huxtable Middleware Architect Core Middleware Information Technology, a division of Information Services The University of Kansas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
