OK this should do the job: https://svn.apache.org/repos/asf/maven/sandbox/trunk/maven/maven-plugin-enforcer
For M3, drop it in the lib folder and just add -Dforce.plugins=gId:aId:ver,gId:aId,ver,etc groupId defaults to org.apache.maven.plugins if omitted -Stephen 2009/11/3 Stephen Connolly <stephen.alan.conno...@gmail.com>: > On 2009-11-03, at 17:50-something, Benjamin Bentmann wrote: >> >>> 2009/11/2 Jason van Zyl <ja...@sonatype.com> >>> >>>> >>>>>> I'm sure we could find a clean place to inject an override for the >>>>>> default >>>>>> version of the compiler plugin in 3.x and then use that version of >>>>>> Maven >>>>>> to >>>>>> build as many on the grid as we can. Can't think of a better way to >>>>>> test >>>>>> a >>>>>> core plugin to make sure we don't hose anyone. >>>>>> >> >> How about this: We implement some lifecycle participant, let's call it the >> PluginVersionEnforcer, that would listen for afterProjectsRead() and iterates >> over all projects in the session in order to mutate plugin versions in their >> models. >> >> This lifecycle participant could be reused for all kinds of plugins if it >> gets >> configured via execution properties, that it can read from the session, e.g. >> >> -Dorg.apache.maven.plugins:maven-compiler-plugin=2.1-SNAPSHOT >> >> which could be added to the configuration of grid builds. >> >> This participant would be some little JAR that we could drop into a regular >> Maven 3.x distro on the grid. >> >> >> Benjamin > > +1 > > -Stephen > > P.S. hopefully your SMTP server gets working soon > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
