Since Maven 2.0.9 (I believe) Maven comes with fixed version for some
plugins. This is done through a pluginManagement section in the super POM.
Thus, you can change these values by overriding them in your pom. However,
this is by no means a complete set and only includes the common ones. You
can have a look yourself if you check out the file pom-4.0.0.xml which can
be found in Maven's über jar (maven-2.2.1-uber.jar for Maven 2.2.1) in teh
Maven distro.
Best practise is still to do this in pluginManagement in your project (in
some parent pom)! One reasons is that the set in the super pom is not
complete. Another is that changing Maven version will otherwise also change
some plugin versions.

/Anders

On Thu, Oct 22, 2009 at 13:42, Rebholz Paul <paul.rebh...@six-group.com>wrote:

> hello maven users
>
> these days I was trying to figure out if maven 2.2.1 comes with a
> version-fixed set of plugins, i.e. if there is an inherent pom which
> fixes this.
>
> We are building our SW with maven and want to make sure that using maven
> 2.2.1 yields the same results right now as it would in the future, in
> other words, is there a guarantee that - out of the box - no newer
> plugin versions are used in the future?
>
> Is there someone out there who can confirm this?
>
> Regards, Paul
>
> This message is for the named person's use only. It may contain
> confidential, proprietary or legally privileged information. If you receive
> this message in error, please notify the sender urgently and then
> immediately delete the message and any copies of it from your system. Please
> also immediately destroy any hardcopies of the message.
> The sender's company reserves the right to monitor all e-mail
> communications through their networks.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Reply via email to