[#MRELEASE-427] Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0) - jira.codehaus.org

Maven 2.x Release Plugin

Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0)

Created: 16/Mar/09 07:23 PM Updated: 01/Feb/10 11:30 AM Resolved: 19/Mar/09 04:25 PM

Return to search

Component/s:

scm

Affects Version/s:

2.0-beta-8

Fix Version/s:

2.0-beta-9

Time Tracking:

Not Specified

Environment:

svn version > 1.5.0

Issue Links:

Related

This issue relates to:

MRELEASE-514 release:branch hit remoteTagging problem

~~MRELEASE-434~~ Assumes scm.url is Current Directory for Remote Tagging

~~MRELEASE-375~~ release plugin does not work with subversion > 1.5.0

~~MRELEASE-443~~ Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0 in release:branch)

This issue is related to:

~~SCM-262~~ scm:tag for subversion tagging from local version of code, not directly from repository

~~SCM-406~~ scm tag does not work with Subversion 1.5.1

Description

« Hide

Due to an issue with svn > 1.5.0, release plugin doesn't work. The scm (1.2) implements a new remote tagging mechanism as a workaround.

Sort Order:

Olivier Lamy made changes - 16/Mar/09 07:25 PM

Field	Original Value	New Value
Link		This issue is related to ~~SCM-406~~ [ ~~SCM-406~~ ]

Olivier Lamy made changes - 16/Mar/09 07:25 PM

Link

This issue is related to ~~SCM-262~~ [ ~~SCM-262~~ ]

Olivier Lamy made changes - 16/Mar/09 07:31 PM

Link

This issue relates to ~~MRELEASE-375~~ [ ~~MRELEASE-375~~ ]

[ Permalink | « Hide ]

Olivier Lamy added a comment - 16/Mar/09 07:35 PM

fixed rev 755056

The mojo configuration is :

<plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-release-plugin</artifactId>
        <version>2.0-beta-9-SNAPSHOT</version>
        <configuration>
          <remoteTagging>true</remoteTagging>
        </configuration>
      </plugin>

Or -DremoteTagging=true.

Olivier Lamy made changes - 16/Mar/09 07:35 PM

Assignee		Olivier Lamy [ olamy ]
Resolution		Fixed [ 1 ]
Fix Version/s		2.0-beta-9 [ 14682 ]
Status	Open [ 1 ]	Closed [ 6 ]

[ Permalink | « Hide ]

Benjamin Bentmann added a comment - 17/Mar/09 04:10 AM

One of Maven's goals is to support "convention over configuration". In this sense, wouldn't it be better if we made remoteTagging=true the default? I mean if the default configuration does simply not work reliably with Subversion > 1.5.0, what's the default good for then?