[
https://issues.apache.org/jira/browse/SCM-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961781#comment-17961781
]
ASF GitHub Bot commented on SCM-491:
------------------------------------
jira-importer commented on issue #703:
URL: https://github.com/apache/maven-scm/issues/703#issuecomment-2964614119
**[Mark
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
commented
this should be fixed by
MRELEA[SE-501](https://issues.apache.org/jira/browse/SE-501)
Please use the localCheckout option to use a file:// clone from the local
repo instead of going over the network:
mvn release:perform -DlocalCheckout=true
> release:perform with Mercurial performs a full hg clone from the remote
> repository
> ----------------------------------------------------------------------------------
>
> Key: SCM-491
> URL: https://issues.apache.org/jira/browse/SCM-491
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-mercurial (hg)
> Reporter: Fabrizio Giudici
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 1.3
>
>
> Hello.
> When executing a release:perform, Maven forces hg to perform a clone of the
> remote repository in the target/checkout directory:
> [INFO] EXECUTING: /bin/sh -c cd /home/hudson/Builds/jrawio~TEST/target && hg
> clone -r 1.5.4 https://@kenai.com/hg/jrawio~src
> /home/hudson/Builds/jrawio~TEST/target/checkout
> Hg repos can be huge (even gigabytes) and thus operation causes a waste of
> bandwidth (and of time). It seems that the most obvious thing to do is to
> clone from the local copy in the main directory (e.g. hg clone -r 1.5.4 ..)
> and if you need to do a laster push you can explicitly specify the URL of the
> remote repository to the hg push command.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
