[ http://jira.codehaus.org/browse/MRELEASE-169?page=comments#action_76763 ] Daniel Nilsson commented on MRELEASE-169: -----------------------------------------
Hi! Mayby a prepare-commit-rollback scenario would work. Ie you first do a release:prepare (which makes a couple of temporary files, copies of existing pom etc, test tagging in scm etc) This anyhow changes the pom.xml to the new state. release:commit actually carries out the changes in all files, tags in scm etc. release:rollback can be used after release:prepare has been done, but a user regrets his action.This target restores the project state to the same as before the prepare-target was executed. -Daniel > Provide a mechanism to undo the effects of prepare > -------------------------------------------------- > > Key: MRELEASE-169 > URL: http://jira.codehaus.org/browse/MRELEASE-169 > Project: Maven 2.x Release Plugin > Issue Type: New Feature > Affects Versions: 2.0-beta-4 > Environment: XP > Reporter: David Hoffer > > Sometimes you don't know if your prepare will work until you try it. In > these cases the dryRun option does not find the failures, examples are bad > paths in the scm section. > It would be nice if the release plugin could undo the changes that the > prepare action caused. Currently, in a multi-module project there are a lot > of files to manually fix if this happens. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
