Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of niall.pemberton@gmail.com
 designates 209.85.214.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=VLo3ZuP8Prwdrw6nhckhMrnDt8SNJXSiVG11cadNoGUuFs8v6/81EjYaYnqZ75q/QE
         NQe/uBAp4V/odRHB2L49TC+ztRpxlwbqGmpTM6roCR6qgcgrIhH5EI4c17jeP6cPZMjw
         sLqj8QqHUa5kfUOExxhgVcawvmqXB4aGUgElE=
MIME-Version: 1.0
Date: Thu, 7 Oct 2010 02:46:23 +0100
Message-ID: <AANLkTimONN1C9TBCgcEDUZjiq2eZLszvchuH8yaGZ5E6@mail.gmail.com>
Subject: [all] Preparing for Maven 3
From: Niall Pemberton <niall.pemberton@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

The vote for Maven 3 is underway - http://markmail.org/message/4itian33hycyt4iz

I have tested the builds for all the components in trunks-proper
(using mvn -Prc clean package) and they worked, except for test
failures with configuration, email and jci - but I get those using m2
as well.

Theres an issue with the commons-build-plugin which I need to look at
and I had a problem with the gpg plugin when doing mvn -Prc install on
a component. Probably the biggest issue though is getting the sites
working. The <reporting> section is deprecated in m3 and reports need
to be configured differently and a new (m3 specific) version of the
site plugin used. I've tried this out adding "m3" profiles to branches
of commons-parent and chain:
    https://svn.apache.org/repos/asf/commons/proper/commons-parent/branches/maven-3-test/
    https://svn.apache.org/repos/asf/commons/proper/chain/branches/test-maven3-profile/

The above have a profile which *activates* when m3 is used - as described here:
    https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html

This profile approach to support both m2 and m3 is one way - but would
create a mess of duplicated configuration in all poms. It would be
much cleaner and less maintenance if we just adopted m3 and dropped m2
support :)

I guess it will take a while for a consensus on this (if ever) but its
something to consider. In the meantime there is stuff we can do to
prepare for m3. It would be good to put reporting plugins into the
<pluginManagement> section of commons-parent. Quite a few components
are on old versions of reporting plugins, so testing and upgrading to
the latest would be good. The one I had most problems with was
Checkstyle - details in the commit log:
    http://svn.apache.org/viewvc?view=revision&revision=1005273

Niall

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org