[ http://jira.codehaus.org/browse/SCM-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241130#action_241130 ]
Sean Flanigan commented on SCM-475: ----------------------------------- The fix for SCM-444 was to add a pushChanges flag in rev 922043. If pushChanges==false, no push. Could we please get support for this flag in the hg plugin? > 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 > Reporter: Benson Margulies > > 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