maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (JIRA)" <>
Subject [jira] (MRELEASE-431) Configuration of policy for calculating next (release) version
Date Mon, 16 Sep 2013 08:39:52 GMT


Robert Munteanu commented on MRELEASE-431:

[~rfscholte] - thanks for the info, I just wanted to know if you'd like any changes made in
the short term. I fully agree that - being published API - we need to get it right the first

{quote} Another thing on my mind: should the API support methods to make it a major, minor
or bugversion increase, or leave that up to the implementation{quote}

I guess we could, but maybe as part of another utility class, to keep the VersionPolicyManager
API clean. Not sure if that needs to be API though, or we could simply  provide it as a convenience
for implementors.
> Configuration of policy for calculating next (release) version
> --------------------------------------------------------------
>                 Key: MRELEASE-431
>                 URL:
>             Project: Maven Release Plugin
>          Issue Type: New Feature
>          Components: prepare
>    Affects Versions: 2.0-beta-8
>            Reporter: Carsten Ziegeler
>            Assignee: Robert Scholte
>             Fix For: 2.5
>         Attachments: 0001-MRELEASE-431-Configuration-of-policy-for-calculating.patch,
MRELEASE-431.patch, MRELEASE-431-v2.patch
> Currently, when preparing the release, the version to release is always the next version
which usually is the current version without the snapshot extension.
> There are quiet a lot projects (Apache Felix, Sling and others) following an even release
numbering policy. So while the current development version is odd (like 1.2.3-SNAPSHOT), the
next released version will be 1.2.4.
> It would be nice if this could be made configuration through some configuration property
> <versionPolicy>next-even</versionPolicy> (with possible values being: next
(default, as-is), next-even, next-odd
> I briefly scanned through the code and it seems that adding support for this requires
changes in both, the release-manager and the release-plugin.
> If this feature gets accepted and if someone could give me some minor hints how/where
to add this I could come up with a patch.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message