You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/03/28 14:58:02 UTC

[jira] [Commented] (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=17069501#comment-17069501 ] 

Hudson commented on MNG-5576:
-----------------------------

Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4

See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/

> 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
>            Priority: Major
>             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
(v8.3.4#803005)