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 plugin should at least display the inherited version number (beginning with maven 2.0.9 where the super-pom fixed the plugin versions). I might be wrong, but globally specifying is not the responsability of the enforcer plugin. Enforcer will just check what you ask it to. Global specification is to be put in dependency/pluginManagement. Cheers. 2008/12/12 Nick Stolwijk <[email protected]> > 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~ > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
