[jira] (MRELEASE-431) Configuration of policy for calculating next (release) version

["Ziga Gregoric (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MRELEASE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328897#comment-328897 ] 

Ziga Gregoric commented on MRELEASE-431:
----------------------------------------

While trying to stick to http://semver.org for a 'pre-release' as in {{1.0.0-alpha.1}}, maven would increase it to {{1.0.1-alpha.1}} instead of {{1.0.0-alpha.2}}. 

Since {{1.0.0-alpha1}} is increased to {{1.0.0-alpha2}}, I was hoping we can have default versioning policy accept notation for 'pre-release' with a dot as delimiter after alpha/beta/milestone. 

MRELEASE-797 is marked as a duplicate, therefore please excuse a non maven committer if this belongs to a new issue. Thank you.

                
> Configuration of policy for calculating next (release) version
> --------------------------------------------------------------
>
>                 Key: MRELEASE-431
>                 URL: https://jira.codehaus.org/browse/MRELEASE-431
>             Project: Maven 2.x Release Plugin
>          Issue Type: New Feature
>          Components: prepare
>    Affects Versions: 2.0-beta-8
>            Reporter: Carsten Ziegeler
>         Attachments: 0001-MRELEASE-431-Configuration-of-policy-for-calculating.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 like
> <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: http://www.atlassian.com/software/jira