[
https://jira.codehaus.org/browse/MRELEASE-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fred Cooke reopened MRELEASE-816:
---------------------------------
See previous comment re consistency. There are at least two possible fixes:
1) Remove space from first commit
2) Add space to second commit
Clearly the latter is preferred as it works around the inability to add space
yourself and is something that pretty much everyone would always want.
> Various issues with scmCommentPrefix value
> ------------------------------------------
>
> Key: MRELEASE-816
> URL: https://jira.codehaus.org/browse/MRELEASE-816
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.3.2
> Environment: Debian Linux OpenJDK 7 mvn 3.0.4
> Reporter: Fred Cooke
> Assignee: Robert Scholte
> Priority: Minor
>
> When the {{ <scmCommentPrefix> }} property is specified the trailing space is
> ignored/trimmed for one of the steps and used for the other. When not
> specified the [maven-release-plugin] has a trailing space for both commit
> messages. For example:
> Releasing sticky-deployer-embedded at 0.8-SNAPSHOTprepare for next
> development iteration
> Releasing sticky-deployer-embedded at 0.8-SNAPSHOT copy for tag
> sticky-deployer-embedded-0.8
> Versus:
> [maven-release-plugin] prepare for next development iteration
> [maven-release-plugin] prepare release 0.1
> Additionally, the version substituted into ${project.version} in this config
> is the SNAPSHOT version from before the release. The tagNameFormat value uses
> the @{project.version} variant to get around this, however if you try to use
> that in the scmCommentPrefix field you get an error.
> Ideally I'd like to set it up like this and have the trailing space respected
> for both commits, and the release version used:
> <scmCommentPrefix>Releasing ${project.artifactId} version @{project.version}:
> </scmCommentPrefix>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
