[
https://issues.apache.org/jira/browse/SCM-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964819#comment-17964819
]
Olivier Lamy commented on SCM-631:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#840|https://github.com/apache/maven-scm/issues/840].
> Mercurial SCM provider works with repository like centralized SCM's do
> ----------------------------------------------------------------------
>
> Key: SCM-631
> URL: https://issues.apache.org/jira/browse/SCM-631
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-mercurial (hg)
> Affects Versions: 1.6
> Environment: Ubuntu 11.04/ArchLinux
> Maven 3.0.3
> Mercurial 1.7.5/1.9.1
> Reporter: Alexander Betaev
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 1.6
>
> Attachments: maven-scm-plugin.patch, maven-scm.patch
>
>
> Mercurial SCM provider works with repositories as if it is centralized SCM:
> all operations are preceeded by "Clone" operation.
> I assume that it should be very useful to put an option which switches
> behaviour and turns off work with central repo.
> Please look at the patch in attachment. I have turned pushChanges flag into
> option I describe. It works for 'update' and 'checkout' operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
