maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Pozolotin (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-431) Configuration of policy for calculating next (release) version
Date Sun, 07 Apr 2013 00:20:53 GMT

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

Andrei Pozolotin commented on MRELEASE-431:
-------------------------------------------

maven should implement semantic versioning in the core

http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf

some plugins which are doing this:

https://github.com/apache/aries/tree/trunk/versioning

https://github.com/jeluard/semantic-versioning


                
> 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
>
> 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

Mime
View raw message