I'm working on the release plugin this week so that it is a bit friendlier with rewriting, and so that it does a better job of populating versions for you.
As for the pertest thing, that's a regression that should be filed and fixed (I guess by making both valid now). There is an open bug to rename pertest - please add a comment to that and we'll give it a sensible name + the old options. - Brett On 4/10/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote: > Lock down the versions of your plugins with <build><pluginManagement>, > either: > - manually > - by using the release plugin (warning: currently that rewrites all your > pom's and removed comments, schema declarations, reorders dependencies, etc) > > With kind regards, > Geoffrey De Smet > > > Jörg Schaible wrote: > > Hello folks, > > > > what is the best way to ensure reproducible releases in M2? By default > > Maven will update its plugins and dependencies from time to time - which is > > fine as long as I work on the trunk. But when I release an artifact, I must > > freeze the current set of plugins/versions for this release - how can I > > achieve that? > > > > Otherwise M2 might just break the reproducibility of such a release - as it > > happened for me today with the new surefire plugin: forkMode "perTest" was > > renamed in the latest release to "pertest". Any release done with the old > > version is not longer reproducible! The build is broken, because the new > > version of the plugin fails with an unknown fork mode. > > > > - Jörg > > > --------------------------------------------------------------------- > 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]
