maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol (JIRA)" <>
Subject [jira] [Commented] (MNG-5576) Allow continuous delivery friendly versions
Date Mon, 29 Aug 2016 16:17:20 GMT


Vincent Massol commented on MNG-5576:

furthermore if you use ${project.version} from where should it be taken?

>From the resolved project's version.

What I don't understand and my comment is for this issue, not another one (otherwise I'd have
created it elsewhere...), is why the restriction on {{revision}}, {{sha1}} and {{changelist}}
property names. 

Re the list I'm not subscribed to the list (not been for years now) and I don't intend to
join it. This was just a one-off question related to a specific jira issue.

> Allow continuous delivery friendly versions
> -------------------------------------------
>                 Key: MNG-5576
>                 URL:
>             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

View raw message