You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2014/03/10 17:16:59 UTC

[jira] (MNG-5576) Allow continuous delivery friendly versions

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

Jason van Zyl commented on MNG-5576:
------------------------------------

There is nothing to use per se, it just prevents the warning when using the ${changelist}, ${revision}, and ${sha1} in the version. It is not specifically related to the maven-release-plugin. This is not directly related to the maven-release-plugin as the maven-release-plugin cannot be used for continuous delivery because it requires rebuilding.

> Allow continuous delivery friendly versions
> -------------------------------------------
>
>                 Key: MNG-5576
>                 URL: https://jira.codehaus.org/browse/MNG-5576
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>    Affects Versions: 3.1.1
>            Reporter: Jason van Zyl
>             Fix For: 3.2.1
>
>
> Currently warnings will be emitted when there are expressions in versions, a few exceptions should be deemed valid to make continuous delivery easier. The use case is to allow easy versioning of an entire multi-module build that can take a version from an external source like SCM. These are the types of exceptions that will be allowed:
> 1.0.0.$\{changelist}
> 1.0.0.$\{revision}
> 1.0.0.$\{sha1}
> When a whole build is versioned like this we can avoid churning the POMs in the SCM which makes it a lot easier to see the actual changes in the project. Not a complete solution for continuous delivery but is a step in the right direction and doesn't interfere with currently behavior as it is currently allowed, just warned against.



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