[
https://jira.codehaus.org/browse/MRELEASE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332400#comment-332400
]
Robert Munteanu commented on MRELEASE-431:
------------------------------------------
[~rscholte] - I'm not sure what you mean. I was able to test the newly-supplied
odd/even release scheme by:
1. Installing my local copy of the plugin
2. Adding the following to the pom file
{code}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<versionPolicyManager
implementation="org.apache.maven.shared.release.phase.OddEvenVersionPolicyManager"/>
</configuration>
</plugin>
{code}
3. Running {{mvn
org.apache.maven.plugins:maven-release-plugin:2.4.2-SNAPSHOT:prepare}}
I've used the expanded g:a:v:goal syntax to avoid declaring snapshot
dependencies on the pom.xml . And for me it works as expected, and matches your
comment #5 about using Plexus configuration.
> 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
