[ 
https://issues.apache.org/jira/browse/MRELEASE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MRELEASE-709:
------------------------------------
    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:
{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}

  was:
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: http://jira.codehaus.org/browse/SCM-631
Also look at http://jira.codehaus.org/browse/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


> Release plugin does not work with central repository and always performs 
> clone operation
> ----------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-709
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-709
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>          Components: perform, prepare, scm
>    Affects Versions: 2.2.1
>         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
>         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
(v6.3.4#6332)

Reply via email to