This was the analysis I did that the time:
http://www.nabble.com/releasing-the-enforcer-tt18419873.html#a18419873
-Original Message-
From: Nick Stolwijk [mailto:nick.stolw...@gmail.com]
Sent: Saturday, December 13, 2008 11:35 AM
To: Maven Users List
Subject: Re: Enforce plugin versions
mvn help:effective-pom shows that there is no version declared. So,
somehow, it should be possible to check this. Is it possible to parse
the output of help:effective-pom to create an extra rule to check on
the reporting plugins?
With regards,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus
I'm not sure what you want to achieve. You want to enforce used plugin
versions without specifying them? If so, then I don't think enforcer-plugin
can do that. It's just here to check what was specified, not to modify the
model to put a version.
Which version of maven are you using? The core
Baptiste MATHUS wrote at Freitag, 12. Dezember 2008 16:38:
I'm not sure what you want to achieve. You want to enforce used plugin
versions without specifying them? If so, then I don't think
enforcer-plugin can do that. It's just here to check what was specified,
not to modify the model to
On Fri, Dec 12, 2008 at 7:28 AM, Nick Stolwijk nick.stolw...@gmail.com wrote:
3. Declare reporting plugin in reporting section without a version and
declare a build/pluginmanagement/plugin with a version
- Enforcer plugin doesn't complain.
- help:effective-pom doesn't show a version
On Fri, Dec 12, 2008 at 7:22 PM, Wendy Smoak wsm...@gmail.com wrote:
On Fri, Dec 12, 2008 at 7:28 AM, Nick Stolwijk nick.stolw...@gmail.com
wrote:
3. Declare reporting plugin in reporting section without a version and
declare a build/pluginmanagement/plugin with a version
- Enforcer
The reporting plugin / plugin interaction is a known issue. It's not easy to
solve in the current 2.0.x code and I chose to release it anyway pending a more
thorough fix down the road. Use case 3 is the only time it should show up.
The problem is that when you run site lifecycle phases, the
