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:43 UTC
[jira] [Closed] (MRELEASE-810) When running
ScmCommitDevelopmentPhase the wrong version is presented to the commit log
[ https://issues.apache.org/jira/browse/MRELEASE-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MRELEASE-810.
-----------------------------------
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.
> When running ScmCommitDevelopmentPhase the wrong version is presented to the commit log
> ---------------------------------------------------------------------------------------
>
> Key: MRELEASE-810
> URL: https://issues.apache.org/jira/browse/MRELEASE-810
> Project: Maven Release Plugin
> Issue Type: Bug
> Affects Versions: 2.3.2
> Reporter: Darryl L. Miles
> Priority: Minor
> Attachments: 0001-MRELEASE-810-ScmCommitDevelopmentPhase-include-SNAPS.patch
>
>
> When running ScmCommitDevelopmentPhase the wrong version is presented to the commit log
> When trying to get the default new development commit message to read:
> [maven-release-plugin] prepare for next development iteration 0.0.2-SNAPSHOT
> The default message does not use {0} even though a parameter is presented. I suspect {0} was not used as it was the wrong version number and no one bothered to fix it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)