Maven Enforcer Plugin, default versions (from Super POM) not taken into account

[Rebholz Paul]

Hi

We are setting up an enterprise-wide parent pom in which we lock down
plugin versions. For the Maven 'inherent' set of core plugins, we want
to fallback on the super pom declared versions, but seem to run into a
problem with the enforcer not taking into account those defaults. We are
using the newest final maven version 2.2.1.

The error message we end up with is the following:

...
[INFO] [enforcer:enforce {execution: enforce}]
[WARNING] Rule 1:
org.apache.maven.plugins.enforcer.RequirePluginVersions failed with
message:
Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are not
allowed )
org.apache.maven.plugins:maven-resources-plugin.        The version
currently in use is 2.3
org.apache.maven.plugins:maven-surefire-plugin.         The version
currently in use is 2.4.3
org.apache.maven.plugins:maven-jar-plugin.      The version currently in
use is 2.2
...

Any tips on how to save us from having to duplicate version information
for the core plugins in the enterprise-wide parent pom ?

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-unsubscribe@...
For additional commands, e-mail: users-help@...

[BRIAN FOX-5]

This is absolutely intentional. The best practice is for you to
control your own versions. Yes the super pom introduces a bit of
stability, but at the cost of complacency. If you rely on the defaults
in the super pom it means in a year when you build with a different
version of maven, you have a whole different set of plugins along with
it. That's probably not what you want. It also means when you upgrade
maven core, you drag along potentially a bunch of new plugins and if
something breaks, how can you tell why?

On Thu, Nov 5, 2009 at 1:28 AM, Rebholz Paul <Paul.Rebholz@...> wrote:

> Hi
>
> We are setting up an enterprise-wide parent pom in which we lock down
> plugin versions. For the Maven 'inherent' set of core plugins, we want
> to fallback on the super pom declared versions, but seem to run into a
> problem with the enforcer not taking into account those defaults. We are
> using the newest final maven version 2.2.1.
>
> The error message we end up with is the following:
>
> ...
> [INFO] [enforcer:enforce {execution: enforce}]
> [WARNING] Rule 1:
> org.apache.maven.plugins.enforcer.RequirePluginVersions failed with
> message:
> Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are not
> allowed )
> org.apache.maven.plugins:maven-resources-plugin.        The version
> currently in use is 2.3
> org.apache.maven.plugins:maven-surefire-plugin.         The version
> currently in use is 2.4.3
> org.apache.maven.plugins:maven-jar-plugin.      The version currently in
> use is 2.2
> ...
>
> Any tips on how to save us from having to duplicate version information
> for the core plugins in the enterprise-wide parent pom ?
>
> 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-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...