struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Mitchell" <>
Subject Re: [OT] Ant vs. Maven - convince me! :)
Date Mon, 08 Aug 2005 21:21:15 GMT
That seems to be a common theme.  I just don't understand why people still 
think they have to give up something to use Maven.  Maven is 100% compatible 
with Ant or whatever you are using.  Maven is 100% compatible with your 
current, past, or future file layout.  You *don't* have to mold your project 
layout to what Maven likes.  Maven will gladly use whatever you have.  I 
guarantee that you cannot make a project layout that Maven can't build.

A while ago, Craig posted a very nice summary about the types of people 
commenting on JSF.  He basically outlined 3 scenarios.  I can honestly say 
that the same applies to Maven.

I don't remember word-for-word how it went, but it was something like 

* People who have not even looked at it, and simply repeat what they here 
from other people (who might not have tried it either)

* People who have played with it, but have not done anything serious and 
therefore do not understand the payoff.

* People who have tried it and can tell you *exactly* why they like or don't 
like it.

While I'm in the last category, I'm not the one *doing* the work (this 
time;) it's really up to you.

James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
AIM:   jmitchtx
Skype: jmitchtx

----- Original Message ----- 
From: "Craig McClanahan" <>
To: "Struts Developers List" <>
Sent: Monday, August 08, 2005 4:20 PM
Subject: Re: [OT] Ant vs. Maven - convince me! :)

On 8/8/05, Frank W. Zammetti <> wrote:
> Hi all,
> I've seen comments for a while now how Maven is better than Ant... just a
> few minutes ago James posted that Maven is "just smart software".  I
> didn't want to hijack that thread, hence this new one.

Good plan, that :-).

My biggest concerns about Maven aren't so much technological (although
I don't personally find the tradeoffs of what I get in stuff that
"just works" versus what I give up in flexibility).  My biggest
concern is what's historically gone on with the Maven community (which
might or might not still be the case ... haven't tried to find out)
vs-a-vs user friendliness and support, but (more currently) the
upcoming Maven1 -> Maven2 migration -- or rewrite, if there isn't any
help being provided.

I don't have any projects I work on that require Maven (since the
Jakarta Commons folks tend to do a "maven ant" and check in the
build.xml file as needed).  Ant is sufficient for my needs, so I'd
prefer to keep my life simpler.  The impact of Ant-based development
on others can be addressed by improving support for downloading
dependencies (yes, that is a feature that Maven provides, but is
certainly not limited to Maven).  Beyond that, Maven doesn't offer me
anything I want that is particularly hard to add to a build script


PS:  And yes, Maven1->Maven2 has a lesson there for all of us
proposing Struts 2 approaches that are not backwards compatible,
without thinking through what the migration story might need to look
like :-).

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message