[
http://jira.codehaus.org/browse/MRELEASE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212244#action_212244
]
John Crim commented on MRELEASE-442:
------------------------------------
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:
{code:xml|title=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>
{code}
> scm tag phase ignores custom message (need to use scm 1.3)
> ----------------------------------------------------------
>
> Key: MRELEASE-442
> URL: http://jira.codehaus.org/browse/MRELEASE-442
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-9
> Reporter: Stas Garifulin
> Assignee: Olivier Lamy
> Fix For: 2.0
>
>
> [http://jira.codehaus.org/browse/SCM-460]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
