You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org> on 2007/04/19 20:10:46 UTC

[jira] Closed: (MRELEASE-169) Provide a mechanism to undo the effects of prepare

     [ http://jira.codehaus.org/browse/MRELEASE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse closed MRELEASE-169.
-------------------------------------

         Assignee: Emmanuel Venisse
       Resolution: Fixed
    Fix Version/s: 2.0-beta-5

Done by release:clean and release:rollback mojos

> 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
>            Assignee: Emmanuel Venisse
>             Fix For: 2.0-beta-5
>
>
> 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