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

Posted to issues@maven.apache.org by "Sean Flanigan (JIRA)" <ji...@codehaus.org> on 2011/02/01 01:07:58 UTC

[jira] Commented: (SCM-475) hg plugin insists on 'pushing'

    [ http://jira.codehaus.org/browse/SCM-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253660#action_253660 ] 

Sean Flanigan commented on SCM-475:
-----------------------------------

Could someone please update http://svn.apache.org/viewvc/maven/release/trunk/pom.xml?view=markup to have <scmVersion>1.5</scmVersion>?  That would ensure the next release of maven-release-plugin will pick up the new scm plugin, wouldn't it?

> hg plugin insists on 'pushing'
> ------------------------------
>
>                 Key: SCM-475
>                 URL: http://jira.codehaus.org/browse/SCM-475
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-mercurial (hg)
>    Affects Versions: 1.2, 1.3, 1.4
>            Reporter: Benson Margulies
>            Assignee: Olivier Lamy
>             Fix For: 1.5
>
>         Attachments: SCM-475-maven-scm-provider-hg.patch
>
>
> 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