[
https://issues.apache.org/jira/browse/SCM-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963696#comment-17963696
]
ASF GitHub Bot commented on SCM-929:
------------------------------------
jira-importer opened a new issue, #1153:
URL: https://github.com/apache/maven-scm/issues/1153
**[Alexander
Betaev](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=infestator)**
opened
**[SCM-929](https://issues.apache.org/jira/browse/SCM-929?redirect=false)** and
commented
Plugin cannot work with repositories as if they were central ones. It pushes
and updates data from central repo.
Please take a look at the patch here: SCM-631
Also look at MRELEA[SE-707](https://issues.apache.org/jira/browse/SE-707)
issue. The patch from attachment enables usage of
${project.scm.developerConnection} var.
The attached patch makes plugin to work with repository as if it was
central. The following arguments were used for manual testing:
```
mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
-Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../ release:prepare
mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
-Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../ release:perform
```
---
**Attachments:**
-
[maven-release-plugin.patch](https://issues.apache.org/jira/secure/attachment/12718064/maven-release-plugin.patch)
(_10.57 kB_)
-
[maven-release-plugin.patch](https://issues.apache.org/jira/secure/attachment/12718136/maven-release-plugin.patch)
(_10.04 kB_)
-
[maven-scm.patch](https://issues.apache.org/jira/secure/attachment/12718061/maven-scm.patch)
(_6.62 kB_)
-
[maven-test-project.tar.bz2](https://issues.apache.org/jira/secure/attachment/12718232/maven-test-project.tar.bz2)
(_4.10 kB_)
> Release plugin does not work with central repository and always performs
> clone operation
> ----------------------------------------------------------------------------------------
>
> Key: SCM-929
> URL: https://issues.apache.org/jira/browse/SCM-929
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-mercurial (hg)
> Environment: Ubuntu 11.04/ArchLinux
> Maven 3.0.3
> Mercurial 1.7.5/1.9.1
> vars:
> MAVEN_OPTS="-DaltDeploymentRepository=abetaev::default::file://$HOME/mvn"
> Reporter: Alexander Betaev
> Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: maven-release-plugin.patch, maven-release-plugin.patch,
> maven-scm.patch, maven-test-project.tar.bz2
>
>
> Plugin cannot work with repositories as if they were central ones. It pushes
> and updates data from central repo.
> Please take a look at the patch here: SCM-631
> Also look at MRELEASE-707 issue. The patch from attachment enables usage of
> $\{project.scm.developerConnection} var.
> The attached patch makes plugin to work with repository as if it was central.
> The following arguments were used for manual testing:
> {noformat}
> mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
> -Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../
> release:prepare
> mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
> -Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../
> release:perform
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
