Maven 2.x Release Plugin

scm tag phase ignores custom message (need to use scm 1.3)

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta-9
  • Fix Version/s: 2.0
  • Component/s: prepare
  • Labels:
    None
  • Number of attachments :
    0

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. SCM-460 tag command ignores custom message parameter

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

Improvement - An improvement or enhancement to an existing feature or task. MRELEASE-451 CLONE -scm:tag with scmCommentPrefix

  • 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
Stas Garifulin added a comment -

Maven release manager properly passes custom message formatted with scmCommentPrefix plugin configuration parameter to the scm provider tag command but the scm tag command ignores the message and uses default.

Show
Stas Garifulin added a comment - Maven release manager properly passes custom message formatted with scmCommentPrefix plugin configuration parameter to the scm provider tag command but the scm tag command ignores the message and uses default.
Olivier Lamy made changes -
Field Original Value New Value
Link This issue depends upon SCM-460 [ SCM-460 ]
Olivier Lamy made changes -
Assignee Olivier Lamy [ olamy ]
Fix Version/s 2.0-beta-10 [ 15113 ]
Hide
Permalink
Olivier Lamy added a comment -

fixing this issue need to update scm dependency to 1.3

Show
Olivier Lamy added a comment - fixing this issue need to update scm dependency to 1.3
Olivier Lamy made changes -
Summary scm tag phase ignores custom message scm tag phase ignores custom message (need to use scm 1.3)
Hide
Permalink
Olivier Lamy added a comment -

fix in rev 769983
Thanks

Show
Olivier Lamy added a comment - fix in rev 769983 Thanks
Olivier Lamy made changes -
Resolution Fixed [ 1 ]
Status Open [ 1 ] Closed [ 6 ]
Martin Wagner made changes -
Link This issue is duplicated by MRELEASE-451 [ MRELEASE-451 ]
Hide
Permalink
Julien HENRY added a comment -

Is it possible to release a new version of release plugin? Maven 3 seems to use 2.0-beta-9 as a default and this bug block the release process (I have to force version of release plugin to 2.0-beta-8)

Thanks

Show
Julien HENRY added a comment - Is it possible to release a new version of release plugin? Maven 3 seems to use 2.0-beta-9 as a default and this bug block the release process (I have to force version of release plugin to 2.0-beta-8) Thanks
Hide
Permalink
John Crim added a comment -

This bug previously prevented us from using 2.0-beta-9 (our checkin policy requires issues in commit messages). There are other bugs in 2.0-beta-8, but previously it was the most workable. MRELEASE-526 prevents us from using 2.0.

However, this plugin configuration seems to work. It uses scm 1.3, and seems to solve this issue:

pom.xml
<build>
  <pluginManagement>
    <plugins>
      <plugin>
        <artifactId>maven-release-plugin</artifactId>
        <version>2.0-beta-9</version> <!-- Don't use 2.0: http://jira.codehaus.org/browse/MRELEASE-526 -->
        <dependencies>
          <!-- Per http://jira.codehaus.org/browse/MRELEASE-442, scmCommentPrefix should work for release-plugin 2.0-beta-9
          if scm 1.3 is used. -->
          <dependency>
            <groupId>org.apache.maven.scm</groupId>
            <artifactId>maven-scm-api</artifactId>
            <version>1.3</version>
          </dependency>
        </dependencies>
      </plugin>
    </plugins>
  </pluginManagement>
Show
John Crim added a comment - This bug previously prevented us from using 2.0-beta-9 (our checkin policy requires issues in commit messages). There are other bugs in 2.0-beta-8, but previously it was the most workable. MRELEASE-526 prevents us from using 2.0. However, this plugin configuration seems to work. It uses scm 1.3, and seems to solve this issue: pom.xml <build> <pluginManagement> <plugins> <plugin> <artifactId> maven-release-plugin </artifactId> <version> 2.0-beta-9 </version> <!-- Don't use 2.0: http://jira.codehaus.org/browse/MRELEASE-526 --> <dependencies> <!-- Per http://jira.codehaus.org/browse/MRELEASE-442, scmCommentPrefix should work for release-plugin 2.0-beta-9 if scm 1.3 is used. --> <dependency> <groupId> org.apache.maven.scm </groupId> <artifactId> maven-scm-api </artifactId> <version> 1.3 </version> </dependency> </dependencies> </plugin> </plugins> </pluginManagement>

People

  • Assignee:
    Olivier Lamy
    Reporter:
    Stas Garifulin
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: