[
https://issues.apache.org/jira/browse/MNG-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446484#comment-15446484
]
Karl Heinz Marbaise commented on MNG-5576:
------------------------------------------
You wrote from {{resolved project's}} where should it be defined ? There must
be at least one location where it's need to be defined. So if you take a multi
module build you can define it once in the root of that multi module build. In
the child modules it might be implemented to accept {{project.version}}. So
currently the {{revision}}, {{sha1}} and {{changelist}} is at the moment
defined which means they are allowed to prevent emitting of warnings during the
build and using special properties which can be defined from command line of
from {{.mvn/maven.confg}} file...but this concepts can of course being improved
so you just omit the {{project.version}} completely. My assumption about the
implementation is simply to use properties instead doing much more complicated
things..(For this you might better ask Jason van Zyl).
> 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.4#6332)
