Return-Path: 
 <dev-return-36769-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: (qmail 29315 invoked from network); 27 Jan 2011 09:58:09 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 27 Jan 2011 09:58:09 -0000
Received: (qmail 29144 invoked by uid 500); 27 Jan 2011 09:58:09 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 28953 invoked by uid 500); 27 Jan 2011 09:58:07 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 28946 invoked by uid 99); 27 Jan 2011 09:58:06 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jan 2011 09:58:06 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [209.85.210.178] (HELO mail-iy0-f178.google.com)
 (209.85.210.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jan 2011 09:57:59 +0000
Received: by iyi42 with SMTP id 42so1549155iyi.37
        for <dev@directory.apache.org>; Thu, 27 Jan 2011 01:57:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.171.197 with SMTP id i5mr668283ibz.54.1296122258624; Thu,
 27 Jan 2011 01:57:38 -0800 (PST)
Sender: mail@stefan-seelmann.de
Received: by 10.231.39.141 with HTTP; Thu, 27 Jan 2011 01:57:38 -0800 (PST)
In-Reply-To: <4D413FAF.2000709@gmail.com>
References: <4D413FAF.2000709@gmail.com>
Date: Thu, 27 Jan 2011 10:57:38 +0100
X-Google-Sender-Auth: lkUKGBZ8aWv4pb_CFuZ3Oly_6o0
Message-ID: <AANLkTikXcFTHs0x0GA+q3yqec34jZmP8zSQjxPN1bf_u@mail.gmail.com>
Subject: Re: Maven 3.0 plugin dependencies
From: Stefan Seelmann <seelmann@apache.org>
To: Apache Directory Developers List <dev@directory.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

Hi Emmanuel,

we actually define the plugin versions in the 'project' POM's
pluginManagement section. I already updated the versions there some
days ago. So as soon as the other projects (shared, apacheds, studio)
use the new parent the new plugin versions are used.

The question is if it is good practice, as we need to release a new
'project' POM quite often.

Kind Regards,
Stefan


On Thu, Jan 27, 2011 at 10:49 AM, Emmanuel Lecharny <elecharny@gmail.com> w=
rote:
> Hi guys,
>
> it seems that we are switching to Maven 3.0 completely. There are a few
> things we have to update in our pom.xml.
> 1) Plugins version
> We currently don't define the version of the maven plugin we are using. T=
his
> is something we can add. Here is an example taken from the MINA project :
>
> <!-- Define the version for each of the used jar and maven plugins -->
> <properties>
> <!-- Maven Plugins -->
> <version.api.plugin>2.2.1</version.api.plugin>
> <version.assembly.plugin>2.2-beta-5</version.assembly.plugin>
> <version.bundle.plugin>2.2.0</version.bundle.plugin>
> <version.clean.plugin>2.3</version.clean.plugin>
> <version.compiler.plugin>2.3.2</version.compiler.plugin>
> <version.deploy.plugin>2.5</version.deploy.plugin>
> <version.gpg.plugin>1.1</version.gpg.plugin>
> <version.jar.plugin>2.3</version.jar.plugin>
> <version.javadoc.plugin>2.7</version.javadoc.plugin>
> <version.jxr.plugin>2.2</version.jxr.plugin>
> <version.model.plugin>2.2.1</version.model.plugin>
> <version.project.plugin>2.2.1</version.project.plugin>
> <version.rat.maven.plugin>1.0-alpha-3</version.rat.maven.plugin>
> <version.release.plugin>2.1</version.release.plugin>
> <version.remote.resources.plugin>1.1</version.remote.resources.plugin>
> <version.site.plugin>2.1</version.site.plugin>
> <version.source.plugin>2.1.2</version.source.plugin>
> <version.shade.plugin>1.4</version.shade.plugin>
> <version.surefire.plugin>2.7.1</version.surefire.plugin>
> <version.xbean.plugin>2.7.1</version.xbean.plugin>
> ...
>
> 2) Update versions
>
> Running mvn versions:display-plugin-updates on the project, I get this li=
st
> of version we can update :
> [INFO] =C2=A0 maven-surefire-report-plugin ......................... 2.7.=
1 ->
> 2.7.2
> [INFO] =C2=A0 org.apache.felix:maven-bundle-plugin ................. 2.1.=
0 ->
> 2.2.0
> [INFO] =C2=A0 maven-surefire-plugin .................................. 2.=
6 ->
> 2.7.1
> [INFO] =C2=A0 maven-antrun-plugin ...................................... =
1.5 ->
> 1.6
> [INFO] =C2=A0 org.codehaus.mojo:antlr-maven-plugin ..................... =
2.1 ->
> 2.2
> [INFO] =C2=A0 maven-assembly-plugin ............................. 2.2-bet=
a-5 ->
> 2.2
> [INFO] =C2=A0 maven-release-plugin ..................................... =
2.0 ->
> 2.1
> [INFO] =C2=A0 maven-site-plugin ............................... 2.1.1 ->
> 3.0-beta-3
> [WARNING] =C2=A0 com.agilejava.docbkx:docbkx-maven-plugin ...............
> (unknown)
>
> --
> Regards,
> Cordialement,
> Emmanuel L=C3=A9charny
> www.iktek.com
>
>