You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/09/06 22:46:17 UTC

[jira] [Closed] (MRELEASE-192) Place the generated backup into the scm tag

     [ https://issues.apache.org/jira/browse/MRELEASE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MRELEASE-192.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Place the generated backup into the scm tag
> -------------------------------------------
>
>                 Key: MRELEASE-192
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-192
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>          Components: rollback
>            Reporter: Edwin Punzalan
>
> Currently, a _release:rollback_ is only possible in the machine where the backup files were generated.  This is a problem especially if these backup files were already deleted in the machine.
> As suggested by jvz, creating and placing the backup jar (just the poms in the same directory structure) will make sure that the backup is available to anyone who wants to revert the release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)