Yes, there is a superpom in Maven, which only changes between Maven
versions. In there are all the plugins Maven binds by default to its various
lifecycles and packagings.

If you want to make sure you can control your build, create a company pom
and use the enforcer to ensure the maven version and plugin versions.

[1] http://www.sonatype.com/people/2008/04/maven-209-released/
[2] http://maven.apache.org/plugins/maven-enforcer-plugin/

Hth,
Nick Stolwijk
~Java Developer~

IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl


On Thu, Oct 22, 2009 at 1:42 PM, 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