[ajug-members] Maven 2 [was: favorite IDE]

[Ron Cordell]

That has been my experience with Maven as well, complicated by the fact that
not all the plugins behave uniformly. They each have their expectations and
quirkiness that differ from the maven "core" or other plugins. The
implicitness of Maven can make it extremely difficult to debug and maintain.
I think that Maven can be very useful especially in multiple project
settings, but I ripped out Maven and replaced it with Ant in our last
project because it took too much developer time to deal with, and I'm all
about making development easier...

On 8/11/06, Björn Gustafsson <bjorng at gmail.com> wrote:
>
> To me the biggest drawback with Maven 2 is the implicitness of the
> targets.  In Ant your build.xml tells you what you can do with the
> project.  By contrast all the Maven POM file tells you are
> dependencies.  The "targets" are all defined by Maven's conventions,
> and possibly by plugins that you or others supply.
>
> IDEs can help out with this by providing a list of the available
> options for running maven, but at least when you first start using it
> that's not terribly helpful either, as there may be dozens or hundreds
> of them.  Some of them may have unexpected consequences, too, which
> can be difficult to discover without trying them.
>
> The upside of this approach is that once you get used to Maven's
> conventions, you can go to just about any maven project and know how
> to build it.
>
>
> Björn Gustafsson
>
> _______________________________________________
> ajug-members mailing list
> ajug-members at ajug.org
> http://www.ajug.org/mailman/listinfo/ajug-members
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ajug.org/pipermail/ajug-members/attachments/20060811/217a4f9c/attachment.html