[ https://issues.apache.org/jira/browse/MNG-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446287#comment-15446287 ]
Karl Heinz Marbaise commented on MNG-5576: ------------------------------------------ First why using an old issue instead of creating a new one and not discuss this on the dev list?...furthermore if you use {{$\{project.version\}}} from where should it be taken? Apart from that you can use a {{revision}}, {{sha1}} or {{changelist}} etc. in the parent and you can use {{-Drevision=xxxxx}} on command line etc. I would suggest to remove you comment and create either a new issue (feature request) or better start a discussion on the dev list? > 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)