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

Robert Scholte commented on MRELEASE-431:
-----------------------------------------

It looks like we don't now yet if the arguments are complete. I think we can 
expect more arguments. For that reason I'd like to introduce the 
{{VersionPolicyRequest}} a simple pojo. This way the signatures of the manager 
will always stay the same, we just add fields to this requestobject if we want. 
                
> 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

Reply via email to