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 rahul.akolkar@gmail.com
 designates 74.125.92.148 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=DJJIXuqJc6k0dWiSOByRZn5+DWhzGxEUp5R2K30NRvbmfbNi5SfkvmIuUr/5ApYgKM
         eTwR9dG5uC6qFaho2yRbv9UOI1j2VxAwt033mJMBHWhrOV1qlxRJQJjsDTkifVBnx6O0
         rucAEc7NuVZ5aPv85VP+NOECYYo4pD3bpEOc0=
MIME-Version: 1.0
In-Reply-To: 
 <60763112.4198381240929722697.JavaMail.root@spooler6-g27.priv.proxad.net>
References: 
 <1957631186.4196121240929110226.JavaMail.root@spooler6-g27.priv.proxad.net>
	 <60763112.4198381240929722697.JavaMail.root@spooler6-g27.priv.proxad.net>
Date: Wed, 29 Apr 2009 18:08:48 -0400
Message-ID: <ce1f2ea80904291508h528cc4c7o8ef912219c98da90@mail.gmail.com>
Subject: Re: [parent] updating plugins versions and configuration ?
From: Rahul Akolkar <rahul.akolkar@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 28, 2009 at 10:42 AM,  <luc.maisonobe@free.fr> wrote:
> Hello,
>
> Trying to remove an annoying warning from maven, I noticed that commons-p=
arent 11 now uses old versions and deprecated configuration for some plugin=
s.
>
> The things I noticed are the following ones:
>
> version changes:
> =A0maven-gpg-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01.0-alpha-4
> =A0maven-install-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A02.3
> =A0maven-source-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A0 2.1
> =A0maven-assembly-plugin =A0 =A0 =A0 =A0 =A0 =A0 2.2-beta-3
> =A0maven-release-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A02.0-beta-9
> =A0maven-antrun-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A0 1.3
> =A0maven-bundle-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A0 2.0.0
> =A0maven-project-info-reports-plugin 2.1.1
> =A0maven-site-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 2.0-beta-7
> =A0jdepend-maven-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A02.0-beta-2
>
> versions and configuration changes:
> =A0maven-javadoc-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A02.5
> =A0(and <aggregate>false</aggregate> should be removed)
>
> proposed additional plugins:
> =A0maven-changes-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A02.1
> =A0cobertura-maven-plugin =A0 =A0 =A0 =A0 =A0 =A02.2
> =A0clirr-maven-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A02.2.2
> =A0findbugs-maven-plugin =A0 =A0 =A0 =A0 =A0 =A0 2.1
> =A0maven-pmd-plugin =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A02.4
> =A0maven-checkstyle-plugin =A0 =A0 =A0 =A0 =A0 2.2
> =A0(and change headerFile into headerLocation for the components which al=
ready use it)
>
> What about updating commons-parent pom ?
>
<snip/>

Good to move to latest releases except where latest releases are buggy
in a manner that affects us :-) I'd suggest upgrading in the parent
snapshot, making a call for volunteers to try the parent snapshot,
leaving it out for a couple of weeks and then calling a vote (I'll try
to build with the snap parent if you give me a few days).

-Rahul

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