You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alexander Betaev (JIRA)" <ji...@codehaus.org> on 2011/08/31 13:06:32 UTC
[jira] Created: (MRELEASE-709) Release plugin does not work with
central repository and always performs clone operation
Release plugin does not work with central repository and always performs clone operation
----------------------------------------------------------------------------------------
Key: MRELEASE-709
URL: https://jira.codehaus.org/browse/MRELEASE-709
Project: Maven 2.x 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-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: 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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-709) Release plugin does not work with
central repository and always performs clone operation
Posted by "Alexander Betaev (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Betaev updated MRELEASE-709:
--------------------------------------
Attachment: maven-release-plugin.patch
maven-scm.patch
new cleaned up patche.
only -DpushChanges=false is required to perform release in HG SCM locally
maven-scm.patch should be applied to maven-scm project (patches HG SCM provider)
> Release plugin does not work with central repository and always performs clone operation
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-709
> URL: https://jira.codehaus.org/browse/MRELEASE-709
> Project: Maven 2.x 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: 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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-709) Release plugin does not work with
central repository and always performs clone operation
Posted by "Alexander Betaev (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Betaev updated MRELEASE-709:
--------------------------------------
Attachment: maven-test-project.tar.bz2
Example project
> Release plugin does not work with central repository and always performs clone operation
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-709
> URL: https://jira.codehaus.org/browse/MRELEASE-709
> Project: Maven 2.x 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-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: 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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira