[
https://issues.apache.org/jira/browse/SCM-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SCM-929:
-------------------------------
Fix Version/s: waiting-for-feedback
> 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
> 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)
