I just did one yesterday and you pretty much have the steps correct. I opted to check out the tag for the official release build, mimicking release. You just need to be careful that your find and replace only gets what you want. Fortunately for me, we where using 4 digit releases (2.1.0.0) that didn't conflict.
-----Original Message----- From: Pete [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 25, 2006 12:58 PM To: Maven Users List Subject: Maven manual Release steps ? Given that the mvn release:prepare / perform still has known major issues. Does anyone out there have a reliable method for doing a manual release. e.g . 1) Can you just do a search and replace <version>1.0-SNAPSHOT</version> replace with <version>1.0</version> I guess you have to look at each dependency first ? 2) Then check into SCM 3) Then do you do a CVS label / tag 4) Then do you do a second search and replace for <version>1.0< <version>1.0</version> replace with <version>1.1-SNAPSHOT</version> Again I guess you have to look at all dependencies first ? 5) Then check into SCM again ? Any thoughts on how to semi automate the replace steps ? or at least document how to do a manual mvn release. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
