[
https://jira.codehaus.org/browse/MRELEASE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330241#comment-330241
]
Robert Munteanu edited comment on MRELEASE-431 at 8/7/13 9:13 AM:
------------------------------------------------------------------
[~rfscholte] - I _think_ I finally understood what you aimed to get with Plexus
configuration. Please see the [^MRELEASE-431-v2.patch], which configures the
versionPolicyManager as you asked. You can also see the [diff on
github|https://github.com/rombert/release/compare/6de575dd76224c690bfd88375eac88f49ba6d319...HEAD]
Let me know if there are any changes you would like applied, as I'm interested
in getting this in a release.
was (Author: rombert):
[~rfscholte] - I _think_ I finally understood what you aimed to get with
Plexus configuration. Please see the [^MRELEASE-431-v2.patch], which configures
the versionPolicyManager as you asked. You can also see the[diff on
github|https://github.com/rombert/release/compare/6de575dd76224c690bfd88375eac88f49ba6d319...HEAD]
Let me know if there are any changes you would like applied, as I'm interested
in getting this in a release.
> Configuration of policy for calculating next (release) version
> --------------------------------------------------------------
>
> Key: MRELEASE-431
> URL: https://jira.codehaus.org/browse/MRELEASE-431
> 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 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
