You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2011/08/31 14:57:34 UTC
[jira] Updated: (SCM-631) Mercurial SCM provider works with
repository like centralized SCM's do
[ https://jira.codehaus.org/browse/SCM-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated SCM-631:
-----------------------------
Fix Version/s: 1.6
> Mercurial SCM provider works with repository like centralized SCM's do
> ----------------------------------------------------------------------
>
> Key: SCM-631
> URL: https://jira.codehaus.org/browse/SCM-631
> Project: Maven SCM
> 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
> Fix For: 1.6
>
> Attachments: maven-scm-plugin.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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira