You could configure the maven-enforcer-plugin with something like
<bannedPlugins>
<excludes>
<exclude>org.apache.maven.plugins:maven-install-plugin</exclude>
</excludes>
<includes>
<include>org.apache.maven.plugins:maven-install-plugin:2.5.1</include>
</includes>
</bannedPlugins>
but this requires the same good structure and this is executed at the
beginning of every project.
So it is still not a fail-fast solution.
A custom rule which is only executed by the root project and which loops
over all the reactor builds will work as a fail-fast solution, but it is
not the easiest thing to code. Even for me this would probably take a
couple of hours to have a solid rule.
Robert
Op Fri, 08 Nov 2013 21:49:32 +0100 schreef Wayne Fay <wayne...@gmail.com>:
If you have a good structure of your project, you should be able to
lock the
version for these plugins with the pluginManagement. That's by far the
simplest and probably best solution.
Agreed. Perhaps the various rules supported by the enforcer plugin
would be helpful in this regard?
Wayne
---------------------------------------------------------------------
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
