On Wed, Dec 3, 2008 at 5:39 PM, Barrie Treloar <[EMAIL PROTECTED]> wrote: > The alternative is to BRANCH first.
This is very true and we ended up doing this as well. It allows you to lock down your code changes and then do any Maven fix-ups that you need to do before release, without having to do them on the trunk until you're sure they're OK. release:prepare/release:rollback to your heart's content, then once you're really ready to pull the trigger, release:perform and your branch transforms itself into a maintenance branch. Is there a wiki or something for best practices like this? I wish someone had told me about all this before we made all the mistakes that led us to rediscover this best practice on our own. The release plugin is picky enough that it's become another piece of the You Must Follow The Maven Way Or You Will Regret It dogma, but it's not nearly so well documented. - John Stoneham --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
