Stephen Connolly wrote:
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
OK, with some guidance from John I got Maven 3.0-SNAPSHOT (r832795)
including the maven-plugin-enforcer installed on the grid. Configuring a
job to use this Maven installation and adding the property
-Dforce.plugins=maven-compiler-plugin:2.1-SNAPSHOT should get us going
with the new plugin version.
Next question is probably some test plan. Do/can we clone some existing
jobs or do we temporarily switch existing jobs to use the test distro?
The latter is more resource-friendly. As for the job selection, I guess
as a minimum all our own stuff should be subjected to the test.
Comments?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
