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)

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta-8
  • Fix Version/s: 2.0-beta-9
  • Component/s: scm
  • Labels:
    None
  • Environment:
    svn version > 1.5.0
  • Number of attachments :
    0

Description

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.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. SCM-262 scm:tag for subversion tagging from local version of code, not directly from repository

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. SCM-406 scm tag does not work with Subversion 1.5.1

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MRELEASE-375 release plugin does not work with subversion > 1.5.0

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MRELEASE-434 Assumes scm.url is Current Directory for Remote Tagging

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MRELEASE-514 release:branch hit remoteTagging problem

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. 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)

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Olivier Lamy added a comment -

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.

Show
Olivier Lamy added a comment - 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.
Hide
Permalink
Benjamin Bentmann added a comment -

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?

Show
Benjamin Bentmann added a comment - 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?
Hide
Permalink
Olivier Lamy added a comment -

this make sense. Others ?

Show
Olivier Lamy added a comment - this make sense. Others ?
Hide
Permalink
Olivier Lamy added a comment -

reopen to have comments on : true/false which one must be the default value ?

Show
Olivier Lamy added a comment - reopen to have comments on : true/false which one must be the default value ?
Hide
Permalink
Clint Gilbert added a comment -

Does remoteTagging=true work with Subversion 1.4.x? If so, remoteTagging=true should be the default,. since it works with all svn versions.

Show
Clint Gilbert added a comment - Does remoteTagging=true work with Subversion 1.4.x? If so, remoteTagging=true should be the default,. since it works with all svn versions.
Hide
Permalink
Olivier Lamy added a comment -

yes it works with 1.4.x.
I have tested the following :

  • cygwin svn 1.4.6 and 1.5.1
  • solaris svn 1.4.6 and 1.5.4
Show
Olivier Lamy added a comment - yes it works with 1.4.x. I have tested the following : cygwin svn 1.4.6 and 1.5.1 solaris svn 1.4.6 and 1.5.4
Hide
Permalink
Olivier Lamy added a comment -

option true by default rev 756209

Show
Olivier Lamy added a comment - option true by default rev 756209
Hide
Permalink
Pablo added a comment -

I have the same problem when executing mvn release:branch.

It would be useful to add the -DremoteTagging argument also when making branches. Thank you.

Show
Pablo added a comment - I have the same problem when executing mvn release:branch. It would be useful to add the -DremoteTagging argument also when making branches. Thank you.
Hide
Permalink
Olivier Lamy added a comment -

please create a new issue!

Show
Olivier Lamy added a comment - please create a new issue!
Hide
Permalink
werner mueller added a comment -

an issue related to branching was created: MRELEASE-514

Show
werner mueller added a comment - an issue related to branching was created: MRELEASE-514

People

  • Assignee:
    Olivier Lamy
    Reporter:
    Olivier Lamy
Vote (0)
Watch (11)

Dates

  • Created:
    Updated:
    Resolved: