You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2019/09/24 13:42:00 UTC
[jira] [Created] (MRELEASE-1028) OddEven release policy does not
support qualifiers in versions
Robert Munteanu created MRELEASE-1028:
-----------------------------------------
Summary: OddEven release policy does not support 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
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)