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 and reporting plugins 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 Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Fri, Dec 12, 2008 at 9:53 PM, Brian E. Fox <bri...@reply.infinity.nu> wrote: > 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 reporting plugins > are injected into the model in the plugin section, so there's no way for me > to tell them apart. There's an open jira for this. > > -----Original Message----- > From: Nick Stolwijk [mailto:nick.stolw...@gmail.com] > Sent: Friday, December 12, 2008 9:28 AM > To: Maven Users List > Subject: Enforce plugin versions and reporting plugins > > I've been trying to enforce my plugin versions with the enforcer > plugin and this works fine for plugins used during the build, but I am > a bit confused about the plugins used by the reporting section. > > A few cases: > > 1. Declare reporting plugin in reporting section without a version > -Enforcer plugins fails on plugin without a version > - help:effective-pom doesn't show a version > > 2. Declare reporting plugin in reporting section with a version > - Enforcer plugin doesn't complain. > - help:effective-pom shows the version > > 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 > > Especially use case 3 seems a bit off. > > I know of the issues with missing reporting/pluginmanagment tag, but > can this be solved in the requirepluginversions rule? > > With regards, > > Nick Stolwijk > ~Java Developer~ > > Iprofs BV. > Claus Sluterweg 125 > 2012 WS Haarlem > www.iprofs.nl > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org