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 (nike.apache.org: domain of niall.pemberton@gmail.com
 designates 209.85.220.218 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=WLRU0c2e+uOEy8cDxQ2+i+0JIslGS830YAKArFmzLJqHDTDoOdaupdtM7F9HYXYuTY
         YGTylVc26U7FyfjYGbfzGJFhQ6FaIa9/jv9TNKJxw4kTsPBExiCEuftn8nV011tCrzKS
         MYt0hTTXH2jhWgCo9VrIhGVx+Oc8El9rHATec=
MIME-Version: 1.0
In-Reply-To: 
 <757059385.4838401267000160691.JavaMail.root@spooler6-g27.priv.proxad.net>
References: 
 <1554008574.4837841266999968712.JavaMail.root@spooler6-g27.priv.proxad.net>
	 <757059385.4838401267000160691.JavaMail.root@spooler6-g27.priv.proxad.net>
Date: Wed, 24 Feb 2010 22:39:39 +0000
Message-ID: <55afdc851002241439v12e20fe5te3343a763b191e35@mail.gmail.com>
Subject: Re: [all] Preparing for commons-parent pom release
From: Niall Pemberton <niall.pemberton@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 24, 2010 at 8:29 AM,  <luc.maisonobe@free.fr> wrote:
>
> ----- "Niall Pemberton" <niall.pemberton@gmail.com> a =E9crit :
>
>> I'd like to do a release of the commons-parent pom - primarily to
>> upgrade to the latest commons-build-plugin 1.2 release.
>>
>> I have also upgraded the plugin versions and changed the "rc" &
>> "release" profiles to now only produce the javadocs and not the whole
>> site (this resolves a problem for multi-module components).
>>
>> Are there any other changes or feedback before calling a vote on
>> this?
>
> Do we consider the list of plugins defined in commons-parent fixed or cou=
ld we extend it ? For several components releases, I added myself checkstyl=
e and findbugs checks and thought it helped getting the component in better=
 shape before release. If we decide to include it, we should decide if we g=
o with maven-checkstyle plugin 2.5, which uses checkstyle 5.0 or not. The c=
heckstyle rules configuration files need to be adapted and this requires Ja=
va 5.

Reporting plugins are problematic. If we define something like
checkstyle in the <reporting> section of commons-parent that forces
all components to have a checkstyle report and I believe there are
some components that don't want it. Unfortunately what gets defined in
the <reporting> section AIUI igores anything in <pluginMabagement> -
so theres no point in adding some config there for something like
checkstyle. I believe though that the <reporting> section is being
deprecated from Maven 3 (currently alpha release) and I think we're
supposed to move reports out of the <reporting> section and into the
build section - but I haven't followed up on how that works. If we do
eventually go that route then we might want to reconsider
<pluginManagement>. Another alternative perhaps would be to have a
separate profile with a standard set of reports - if we can find
common ground among enough components.

Niall

> Luc
>
>>
>> Niall

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