[
https://issues.apache.org/jira/browse/MRELEASE-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936807#comment-16936807
]
Robert Munteanu commented on MRELEASE-1028:
-------------------------------------------
/CC [~simone.tripodi] - FYI
> OddEven release policy does not support numeric qualifiers in versions
> ----------------------------------------------------------------------
>
> Key: MRELEASE-1028
> URL: https://issues.apache.org/jira/browse/MRELEASE-1028
> Project: Maven Release Plugin
> Issue Type: Bug
> Reporter: Robert Munteanu
> Priority: Major
>
> We are using {{maven-release-oddeven-policy:2.5.3}} in our projects to
> automate the way our versioning process works.
> We sometimes use project versions which contain two versions, e.g. when
> tracking the version of an API specification or relevant external dependency.
> For instance, Foo Wrapper 1.1.0-1.0.5 is a bundle that wraps Foo version
> 1.0.5 and is itself at version 1.1.0 .
> Assuming a Foo version of 1.0.5, at development time, the bundle version
> would be 1.1.1-1.0.5-SNAPSHOT and at release time 1.1.2-1.0.5 .
> However, the odd/even release policy would propose a release version of
> 1.1.1-2.0.5 at release time. IIUC the change is not in line with how Maven
> defines versios ( 1.0.5 is just a qualifier ) and the release policy should
> be corrected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
