You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Emmanuel Lecharny <el...@gmail.com> on 2011/01/27 10:49:35 UTC

Maven 3.0 plugin dependencies

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. 
This 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 
list of version we can update :
[INFO]   maven-surefire-report-plugin ......................... 2.7.1 -> 
2.7.2
[INFO]   org.apache.felix:maven-bundle-plugin ................. 2.1.0 -> 
2.2.0
[INFO]   maven-surefire-plugin .................................. 2.6 -> 
2.7.1
[INFO]   maven-antrun-plugin ...................................... 1.5 
-> 1.6
[INFO]   org.codehaus.mojo:antlr-maven-plugin ..................... 2.1 
-> 2.2
[INFO]   maven-assembly-plugin ............................. 2.2-beta-5 
-> 2.2
[INFO]   maven-release-plugin ..................................... 2.0 
-> 2.1
[INFO]   maven-site-plugin ............................... 2.1.1 -> 
3.0-beta-3
[WARNING]   com.agilejava.docbkx:docbkx-maven-plugin ............... 
(unknown)

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Maven 3.0 plugin dependencies

Posted by Emmanuel Lecharny <el...@gmail.com>.
On 1/27/11 3:46 PM, Stefan Seelmann wrote:
> On Thu, Jan 27, 2011 at 3:17 PM, Emmanuel Lecharny<el...@gmail.com>  wrote:
>> Hi again.
>>
>> I agree that it does not make a lot of sense to move deps into trunks.
>>
>> We may want to release a new version of the 'project' project with all the
>> changes done those last days.
> Another idea: we can also use the 'project' SNAPSHOT till we release
> one of the big projects. WDYT?

Hmmm, rather use the released version, otherwise we might have troubles.

As we can release the project with a 4 hours notice, I think we just 
need to release when needed.

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Maven 3.0 plugin dependencies

Posted by Emmanuel Lecharny <el...@gmail.com>.
On 1/27/11 4:18 PM, Stefan Seelmann wrote:
> On Thu, Jan 27, 2011 at 4:06 PM, Emmanuel Lecharny<el...@gmail.com>  wrote:
>> On 1/27/11 4:01 PM, Stefan Seelmann wrote:
>>> So let's release version 19 soon.
>> +19 !
> Oh, you have nineteen votes?

Nine ! Oops, nein ;)


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Maven 3.0 plugin dependencies

Posted by Stefan Seelmann <se...@apache.org>.
On Thu, Jan 27, 2011 at 4:06 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
> On 1/27/11 4:01 PM, Stefan Seelmann wrote:
>>
>> So let's release version 19 soon.
>
> +19 !

Oh, you have nineteen votes?

Re: Maven 3.0 plugin dependencies

Posted by Emmanuel Lecharny <el...@gmail.com>.
On 1/27/11 4:01 PM, Stefan Seelmann wrote:
> So let's release version 19 soon.

+19 !


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Maven 3.0 plugin dependencies

Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
+1

On 27 janv. 2011, at 16:01, Stefan Seelmann wrote:

> So let's release version 19 soon.

Re: Maven 3.0 plugin dependencies

Posted by Stefan Seelmann <se...@apache.org>.
On Thu, Jan 27, 2011 at 3:49 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
> On 27 janv. 2011, at 15:46, Stefan Seelmann wrote:
>
>> On Thu, Jan 27, 2011 at 3:17 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
>>> Hi again.
>>>
>>> I agree that it does not make a lot of sense to move deps into trunks.
>>>
>>> We may want to release a new version of the 'project' project with all the
>>> changes done those last days.
>>
>> Another idea: we can also use the 'project' SNAPSHOT till we release
>> one of the big projects. WDYT?
>
> + 1
>
> AFAIR, that's what we used to be doing before.

There is an issue mentioned with using SNAPSHOT parent:
https://cwiki.apache.org/confluence/display/DIRxDEV/Top+Level+Pom+Management+Policy

I just tested it:
- set 19-SNAPSHOT as parent version in 'shared' project
- deleted the ~/.m2/repository/org/apache/directory/project folder
-> Maven throws error: Non-resolvable parent POM: Could not find
artifact org.apache.directory.project:project:pom:19-SNAPSHOT and
'parent.relativePath' points at no local POM

The 19-SNAPSHOT is deployed in the Apache Snapshot repository but it
won't work, the SNAPSHOT must be installed in the local repo.

So let's release version 19 soon.

Kind Regards,
Stefan

Re: Maven 3.0 plugin dependencies

Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
On 27 janv. 2011, at 16:00, Felix Knecht wrote:

> On 01/27/2011 03:49 PM, Pierre-Arnaud Marcelot wrote:
>> On 27 janv. 2011, at 15:46, Stefan Seelmann wrote:
>> 
>>> On Thu, Jan 27, 2011 at 3:17 PM, Emmanuel Lecharny<el...@gmail.com>  wrote:
>>>> Hi again.
>>>> 
>>>> I agree that it does not make a lot of sense to move deps into trunks.
>>>> 
>>>> We may want to release a new version of the 'project' project with all the
>>>> changes done those last days.
>>> 
>>> Another idea: we can also use the 'project' SNAPSHOT till we release
>>> one of the big projects. WDYT?
>> 
>> + 1
>> 
>> AFAIR, that's what we used to be doing before.
> 
> The problem about SNAPSHOT dependencies is, that there's no garantee, that they exists when they are used:
> 
> - Imagine the snapshot repository deletes all snapshots older than X days. So it's very probably that a snapshot isn't available anymore after X days if no svn commit force any CI to deploy a newer snapshot.
> Hence the TLP pom.xml snapshot isn't online available anywhere. How to expalin this to a new user/developer who just did a checkout of the shared module and wants to build it?

Yeah, that's true.
But as the 'project' sub-project is being included in the 'trunks' checkout and being built first, you should not be depending on snapshot repositories.

That said, for the casual user/developer who only checks out 'shared',  as you point out, it can be a problem.

Releasing 'project' is so easy, I guess we shouldn't be shy to release it often, when needed.

Regards,
Pierre-Arnaud

> 
> Regards
> Felix
> 
>> 
>> Regards,
>> Pierre-Arnaud
>> 
>> 
>>> Kind Regards,
>>> Stefan
>> 
>

Re: Maven 3.0 plugin dependencies

Posted by Felix Knecht <fe...@apache.org>.
On 01/27/2011 03:49 PM, Pierre-Arnaud Marcelot wrote:
> On 27 janv. 2011, at 15:46, Stefan Seelmann wrote:
>
>> On Thu, Jan 27, 2011 at 3:17 PM, Emmanuel Lecharny<el...@gmail.com>  wrote:
>>> Hi again.
>>>
>>> I agree that it does not make a lot of sense to move deps into trunks.
>>>
>>> We may want to release a new version of the 'project' project with all the
>>> changes done those last days.
>>
>> Another idea: we can also use the 'project' SNAPSHOT till we release
>> one of the big projects. WDYT?
>
> + 1
>
> AFAIR, that's what we used to be doing before.

The problem about SNAPSHOT dependencies is, that there's no garantee, 
that they exists when they are used:

- Imagine the snapshot repository deletes all snapshots older than X 
days. So it's very probably that a snapshot isn't available anymore 
after X days if no svn commit force any CI to deploy a newer snapshot.
Hence the TLP pom.xml snapshot isn't online available anywhere. How to 
expalin this to a new user/developer who just did a checkout of the 
shared module and wants to build it?

Regards
Felix

>
> Regards,
> Pierre-Arnaud
>
>
>> Kind Regards,
>> Stefan
>

Re: Maven 3.0 plugin dependencies

Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
On 27 janv. 2011, at 15:46, Stefan Seelmann wrote:

> On Thu, Jan 27, 2011 at 3:17 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
>> Hi again.
>> 
>> I agree that it does not make a lot of sense to move deps into trunks.
>> 
>> We may want to release a new version of the 'project' project with all the
>> changes done those last days.
> 
> Another idea: we can also use the 'project' SNAPSHOT till we release
> one of the big projects. WDYT?

+ 1

AFAIR, that's what we used to be doing before.

Regards,
Pierre-Arnaud


> Kind Regards,
> Stefan

Re: Maven 3.0 plugin dependencies

Posted by Stefan Seelmann <se...@apache.org>.
On Thu, Jan 27, 2011 at 3:17 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
> Hi again.
>
> I agree that it does not make a lot of sense to move deps into trunks.
>
> We may want to release a new version of the 'project' project with all the
> changes done those last days.

Another idea: we can also use the 'project' SNAPSHOT till we release
one of the big projects. WDYT?

Kind Regards,
Stefan

Re: Maven 3.0 plugin dependencies

Posted by Emmanuel Lécharny <el...@apache.org>.
On 1/31/11 1:17 PM, Stefan Seelmann wrote:
> On Thu, Jan 27, 2011 at 3:40 PM, Emmanuel Lecharny<el...@gmail.com>  wrote:
>> On 1/27/11 3:31 PM, Felix Knecht wrote:
>>> On 01/27/2011 03:17 PM, Emmanuel Lecharny wrote:
>>>> Hi again.
>>>>
>>>> I agree that it does not make a lot of sense to move deps into trunks.
>>>>
>>>> We may want to release a new version of the 'project' project with all
>>>> the changes done those last days.
>>> Maybe it's worth to wait for the latest Apache pom.xml released soon [1]
>>>
>>>
>>> [1] http://markmail.org/message/c6ml53rozserwopm
>>>
>>>
>>>
>> We are still using version 7 :)
>>
>> What is going to happen if we switch to version 8 first ?
> I updated to version 8. The release of version 9 of the Apache POM
> seems to take some more time, some new Jiras were opened [2].
>
> So I'm going to prepare a release for org.apache.directory.project:project:19.

Great ! Thanks a lot !

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Maven 3.0 plugin dependencies

Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Thanks Stefan!

On 31 janv. 2011, at 13:17, Stefan Seelmann wrote:

> On Thu, Jan 27, 2011 at 3:40 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
>> On 1/27/11 3:31 PM, Felix Knecht wrote:
>>> 
>>> On 01/27/2011 03:17 PM, Emmanuel Lecharny wrote:
>>>> 
>>>> Hi again.
>>>> 
>>>> I agree that it does not make a lot of sense to move deps into trunks.
>>>> 
>>>> We may want to release a new version of the 'project' project with all
>>>> the changes done those last days.
>>> 
>>> Maybe it's worth to wait for the latest Apache pom.xml released soon [1]
>>> 
>>> 
>>> [1] http://markmail.org/message/c6ml53rozserwopm
>>> 
>>> 
>>> 
>> We are still using version 7 :)
>> 
>> What is going to happen if we switch to version 8 first ?
> 
> I updated to version 8. The release of version 9 of the Apache POM
> seems to take some more time, some new Jiras were opened [2].
> 
> So I'm going to prepare a release for org.apache.directory.project:project:19.
> 
> Kind Regards,
> Stefan
> 
> 
> [2] https://issues.apache.org/jira/browse/MPOM

Re: Maven 3.0 plugin dependencies

Posted by Stefan Seelmann <se...@apache.org>.
On Thu, Jan 27, 2011 at 3:40 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
> On 1/27/11 3:31 PM, Felix Knecht wrote:
>>
>> On 01/27/2011 03:17 PM, Emmanuel Lecharny wrote:
>>>
>>> Hi again.
>>>
>>> I agree that it does not make a lot of sense to move deps into trunks.
>>>
>>> We may want to release a new version of the 'project' project with all
>>> the changes done those last days.
>>
>> Maybe it's worth to wait for the latest Apache pom.xml released soon [1]
>>
>>
>> [1] http://markmail.org/message/c6ml53rozserwopm
>>
>>
>>
> We are still using version 7 :)
>
> What is going to happen if we switch to version 8 first ?

I updated to version 8. The release of version 9 of the Apache POM
seems to take some more time, some new Jiras were opened [2].

So I'm going to prepare a release for org.apache.directory.project:project:19.

Kind Regards,
Stefan


[2] https://issues.apache.org/jira/browse/MPOM

Re: Maven 3.0 plugin dependencies

Posted by Felix Knecht <fe...@apache.org>.
On 01/27/2011 03:40 PM, Emmanuel Lecharny wrote:
> On 1/27/11 3:31 PM, Felix Knecht wrote:
>> On 01/27/2011 03:17 PM, Emmanuel Lecharny wrote:
>>> Hi again.
>>>
>>> I agree that it does not make a lot of sense to move deps into trunks.
>>>
>>> We may want to release a new version of the 'project' project with all
>>> the changes done those last days.
>>
>> Maybe it's worth to wait for the latest Apache pom.xml released soon [1]
>>
>>
>> [1] http://markmail.org/message/c6ml53rozserwopm
>>
>>
>>
> We are still using version 7 :)
>
> What is going to happen if we switch to version 8 first ?

Hehe you caught me :-/ I just saw the discussion on the maven/dev list ...

Re: Maven 3.0 plugin dependencies

Posted by Emmanuel Lecharny <el...@gmail.com>.
On 1/27/11 3:31 PM, Felix Knecht wrote:
> On 01/27/2011 03:17 PM, Emmanuel Lecharny wrote:
>> Hi again.
>>
>> I agree that it does not make a lot of sense to move deps into trunks.
>>
>> We may want to release a new version of the 'project' project with all
>> the changes done those last days.
>
> Maybe it's worth to wait for the latest Apache pom.xml released soon [1]
>
>
> [1] http://markmail.org/message/c6ml53rozserwopm
>
>
>
We are still using version 7 :)

What is going to happen if we switch to version 8 first ?

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Maven 3.0 plugin dependencies

Posted by Felix Knecht <fe...@apache.org>.
On 01/27/2011 03:17 PM, Emmanuel Lecharny wrote:
> Hi again.
>
> I agree that it does not make a lot of sense to move deps into trunks.
>
> We may want to release a new version of the 'project' project with all
> the changes done those last days.

Maybe it's worth to wait for the latest Apache pom.xml released soon [1]


[1] http://markmail.org/message/c6ml53rozserwopm

Re: Maven 3.0 plugin dependencies

Posted by Emmanuel Lecharny <el...@gmail.com>.
Hi again.

I agree that it does not make a lot of sense to move deps into trunks.

We may want to release a new version of the 'project' project with all 
the changes done those last days.

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Maven 3.0 plugin dependencies

Posted by Stefan Seelmann <se...@apache.org>.
On Thu, Jan 27, 2011 at 11:07 AM, Emmanuel Lecharny <el...@gmail.com> wrote:
> On 1/27/11 10:57 AM, Stefan Seelmann wrote:
>>
>> 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.
>
> Sh*it, I forgot about it :) Though, we still have some plugins with a
> version defined in shared/pom.xml or apacheds/pom.xml.

Yes, we can remove those versions. The new M3 site plugin defines a
version resolution for reporting plugins [1], which was missing in the
former M2 reporting section.

>> The question is if it is good practice, as we need to release a new
>> 'project' POM quite often.
>
> Good question. Now, Alex has created a "meta" project, in trunks, and may be
> it's a good idea to move what we have in project there. (trunks links to all
> the projects, including Studio)

I don't think that's a good idea. The 'meta' project is only used to
aggregate all sub-projects into a single checkout and build. Whereas
the 'project' parent is used to inherits common properties like
mailing list, team, release profiles, etc. Inheritance and aggregation
are two different beasts [2].

> I'm not even sure that the Project project is such a good idea right now.
> I'm also wondering if we should not keep the dependencies in each
> sub-projects, as it's very likely we will release Shared/LdapAPI separately.

Dependency versions are defined in each sub-project's
dependencyManagement section, and that makes totally sense. But for
plugin versions I think we can use the 'project' parent.

Kind Regards,
Stefan


[1] http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#Version_Resolution
[2] http://maven.apache.org/pom.html

Re: Maven 3.0 plugin dependencies

Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
On 27 janv. 2011, at 11:07, Emmanuel Lecharny wrote:

> On 1/27/11 10:57 AM, Stefan Seelmann wrote:
>> 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.
> Sh*it, I forgot about it :) Though, we still have some plugins with a version defined in shared/pom.xml or apacheds/pom.xml.
>> The question is if it is good practice, as we need to release a new
>> 'project' POM quite often.
> 
> Good question. Now, Alex has created a "meta" project, in trunks, and may be it's a good idea to move what we have in project there. (trunks links to all the projects, including Studio)

Not a good idea to me.
I see this 'trunks' POM exactly as the 'trunk-with-dependencies' POM we used before.
This is just a 'workaround' to gather all the majors sub-projects via SVN externals into a single build process.

Depending on the 'trunks' POM would make a release much more complicated and probably implicates that we release all sub-projects at the same time.

> I'm not even sure that the Project project is such a good idea right now. I'm also wondering if we should not keep the dependencies in each sub-projects, as it's very likely we will release Shared/LdapAPI separately.

I find the 'project' very interesting for storing common configuration to all sub-projects for site generation, plugins management, etc.
I strongly believe each sub-projects needs to define its dependencies on its own because we might not want to always depend on the latest version of one library or another.
For example, until recent modifications, Studio has been using an old version of Shared for around 1,5 year and 3 different releases.

Now, if each version defined in a root POM can be overridden to another version in a sub-project pom it might work as expected.
Maybe something we need to try...

> 
> Something we have to discuss about.
> 
> 
> -- 
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>

Re: Maven 3.0 plugin dependencies

Posted by Emmanuel Lecharny <el...@gmail.com>.
On 1/27/11 10:57 AM, Stefan Seelmann wrote:
> 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.
Sh*it, I forgot about it :) Though, we still have some plugins with a 
version defined in shared/pom.xml or apacheds/pom.xml.
> The question is if it is good practice, as we need to release a new
> 'project' POM quite often.

Good question. Now, Alex has created a "meta" project, in trunks, and 
may be it's a good idea to move what we have in project there. (trunks 
links to all the projects, including Studio)

I'm not even sure that the Project project is such a good idea right 
now. I'm also wondering if we should not keep the dependencies in each 
sub-projects, as it's very likely we will release Shared/LdapAPI separately.

Something we have to discuss about.


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Maven 3.0 plugin dependencies

Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
On 27 janv. 2011, at 10:57, Stefan Seelmann wrote:

> 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.

That's a really good thing.

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

Considering the release of the 'project' POM is very easy, I don't think that's an issue at all.
"Release early, release often"... ;)

> Kind Regards,
> Stefan

Re: Maven 3.0 plugin dependencies

Posted by Stefan Seelmann <se...@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 <el...@gmail.com> wrote:
> 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. This
> 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 list
> of version we can update :
> [INFO]   maven-surefire-report-plugin ......................... 2.7.1 ->
> 2.7.2
> [INFO]   org.apache.felix:maven-bundle-plugin ................. 2.1.0 ->
> 2.2.0
> [INFO]   maven-surefire-plugin .................................. 2.6 ->
> 2.7.1
> [INFO]   maven-antrun-plugin ...................................... 1.5 ->
> 1.6
> [INFO]   org.codehaus.mojo:antlr-maven-plugin ..................... 2.1 ->
> 2.2
> [INFO]   maven-assembly-plugin ............................. 2.2-beta-5 ->
> 2.2
> [INFO]   maven-release-plugin ..................................... 2.0 ->
> 2.1
> [INFO]   maven-site-plugin ............................... 2.1.1 ->
> 3.0-beta-3
> [WARNING]   com.agilejava.docbkx:docbkx-maven-plugin ...............
> (unknown)
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>
>