You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2017/03/12 18:26:04 UTC

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

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

Hervé Boutemy edited comment on MNG-5576 at 3/12/17 6:25 PM:
-------------------------------------------------------------

Implemented on [88d0abcd30a0ab040850b3086b3f0ddd8e9607f3|http://git-wip-us.apache.org/repos/asf/maven/commit/88d0abcd30a0ab040850b3086b3f0ddd8e9607f3]


was (Author: jvanzyl):
Implemented on 88d0abcd30a0ab040850b3086b3f0ddd8e9607f3

> Allow continuous delivery friendly versions
> -------------------------------------------
>
>                 Key: MNG-5576
>                 URL: https://issues.apache.org/jira/browse/MNG-5576
>             Project: Maven
>          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.3.15#6346)