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...@codehaus.org> on 2014/05/02 14:41:10 UTC

[jira] (MCHANGES-242) release: support scmBuildNumber and scmTag attribute

    [ https://jira.codehaus.org/browse/MCHANGES-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345672#comment-345672 ] 

Michael Osipov commented on MCHANGES-242:
-----------------------------------------

You can apply filtering for quite some time which means that you can format your version the way *you* like.

> release: support scmBuildNumber and scmTag attribute
> ----------------------------------------------------
>
>                 Key: MCHANGES-242
>                 URL: https://jira.codehaus.org/browse/MCHANGES-242
>             Project: Maven Changes Plugin
>          Issue Type: Improvement
>          Components: changes.xml
>    Affects Versions: 2.4
>            Reporter: Florian Brunner
>
> I think it's very important to state the buildNumber and the tag of a release in the change log.
> I suggest to add 2 optional attributes to the release element:
> - scmBuildNumber
> - scmTag
> One could then set
> - scmBuildNumber to ${buildNumber} (overriden by Build Number Maven Plugin; initialize to -1?)
> - scmTag to ${tag} (overriden by Maven Release Plugin; initialize to ${project.build.finalName}?)
> Of course this means that filtering should be supported (which would be a good thing anyway).



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)