[jira] Moved: (MRELEASE-641) upgrade to scm 1.5 (hg plugin insists on 'pushing')

["Olivier Lamy (JIRA)" <ji...@codehaus.org>]

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

Olivier Lamy moved SCM-602 to MRELEASE-641:
-------------------------------------------

           Complexity:   (was: Intermediate)
          Component/s:     (was: maven-scm-provider-mercurial (hg))
                       scm
        Fix Version/s:     (was: 1.5)
                       2.2
    Affects Version/s:     (was: 1.4)
                           (was: 1.3)
                           (was: 1.2)
                       2.1
           Issue Type: Improvement  (was: Bug)
                  Key: MRELEASE-641  (was: SCM-602)
              Project: Maven 2.x Release Plugin  (was: Maven SCM)

> upgrade to scm 1.5 (hg plugin insists on 'pushing')
> ---------------------------------------------------
>
>                 Key: MRELEASE-641
>                 URL: http://jira.codehaus.org/browse/MRELEASE-641
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: scm
>    Affects Versions: 2.1
>            Reporter: Olivier Lamy
>            Assignee: Olivier Lamy
>             Fix For: 2.2
>
>
> When I combine the mercurial scm with the release plugin, I'm unhappy to discover that the scm insists on doing a push. The whole point of a hg or git-based systems is to work in the local clone and push up to the repo at a later time. I submit that the plugin should leave the pushing to me, simply performing the hg manipulations in the local clone.

-- 
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