[SCM-929] Release plugin does not work with central repository and always performs clone operation

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: waiting-for-feedback
• Component/s: 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"
• Flags: Patch
• Assignee: Unassigned
• Reporter: Alexander Betaev
• Created: 31/Aug/11 06:04
• Updated: 17/Jul/22 11:39

Description

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:

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