commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell" <>
Subject Happy with Maven1 Was: [Jakarta-commons Wiki] Update of "Maven2MigrationPlan" by MartinCooper
Date Fri, 03 Mar 2006 23:04:05 GMT
That's a very good point. Do we:

1) Want to keep Commons on a unified build system?
2) Want to keep Commons sites on a similar style?
3) Want to only support one build system?

My personal view is that our Maven-1 current build system for Commons
is overly complicated - it needs to be simpler. The Maven-2 proposed
one is definitely better, and we need to make sure we don't get sloppy
and start using unreleased or complex things. Not that we can move to
Maven-2 as things aren't released.

Currently we support Ant and Maven-1; though poorly. We need a CI
system that runs maven ant on the chiefly Maven-1 ones, and warns when
the chiefly Ant ones change build.xml's without an m1 change. I can't
imagine getting away from Ant builds - so unless we go back to Ant
alone, we'll always have 2 systems.

I'd like to get around the issue of keeping the sites similar by
making the sites hugely simpler - another place where we
over-complicate I think.


On 3/3/06, Apache Wiki <> wrote:
> Dear Wiki user,
> You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change
> The following page has been changed by MartinCooper:
> ------------------------------------------------------------------------------
>    * el
>    * email
>    * feedparser
> -  * fileupload
> +  * fileupload - Happy with Maven 1. No interest in moving to Maven 2.
>    * httpclient
>    * io
>    * jelly - m1 Jelly plugin needs moving to Jelly and then converting to an m2 plugin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message