You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Darryl L. Miles (JIRA)" <ji...@codehaus.org> on 2012/12/06 22:05:13 UTC

[jira] (MRELEASE-810) When running ScmCommitDevelopmentPhase the wrong version is presented to the commit log

Darryl L. Miles created MRELEASE-810:
----------------------------------------

             Summary: When running ScmCommitDevelopmentPhase the wrong version is presented to the commit log
                 Key: MRELEASE-810
                 URL: https://jira.codehaus.org/browse/MRELEASE-810
             Project: Maven 2.x Release Plugin
          Issue Type: Bug
    Affects Versions: 2.3.2
            Reporter: Darryl L. Miles
            Priority: Minor


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 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

        

[jira] (MRELEASE-810) When running ScmCommitDevelopmentPhase the wrong version is presented to the commit log

Posted by "Darryl L. Miles (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MRELEASE-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darryl L. Miles updated MRELEASE-810:
-------------------------------------

    Attachment: 0001-MRELEASE-810-ScmCommitDevelopmentPhase-include-SNAPS.patch

Patch on git tree maven-release.git trunk a603d07
                
> When running ScmCommitDevelopmentPhase the wrong version is presented to the commit log
> ---------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-810
>                 URL: https://jira.codehaus.org/browse/MRELEASE-810
>             Project: Maven 2.x 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 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