To enforce that all plugins are versioned use the enforcer plugin [1] with the rule requirePluginVersions [2].
For the dependencymanagement enforcement take a look at the Maven Dependency Plugin [3] with the goals analyze-only [4] and anaylyze-dep-mgt [5]. [1] http://maven.apache.org/plugins/maven-enforcer-plugin/ [2] http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html [3] http://maven.apache.org/plugins/maven-dependency-plugin/ [4] http://maven.apache.org/plugins/maven-dependency-plugin/analyze-only-mojo.html [5] http://maven.apache.org/plugins/maven-dependency-plugin/analyze-dep-mgt-mojo.html Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Mon, Apr 26, 2010 at 5:59 PM, solo1970 <[email protected]> wrote: > > Hello, > > For my project, I need to identify plugins/dependencies that don't have > explicit versions specified (i.e. that would use the latest version) > > Also, I would need a plugin to fail my build if the aggregated modules don't > use the same version of inter-project dependencies. (would check for project > dependency inconsistency) > > Any ideas? > > Sonia > -- > View this message in context: > http://old.nabble.com/Dependency-Management-%2B-tp28366761p28366761.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
