You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2016/01/12 21:12:46 UTC

[jira] [Closed] (MRELEASE-816) Various issues with scmCommentPrefix value

     [ https://issues.apache.org/jira/browse/MRELEASE-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MRELEASE-816.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still persists, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Various issues with scmCommentPrefix value
> ------------------------------------------
>
>                 Key: MRELEASE-816
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-816
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)