[
https://jira.codehaus.org/browse/MRELEASE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326957#comment-326957
]
Robert Scholte commented on MRELEASE-431:
-----------------------------------------
There are at least two options:
- through Plexus Components ( example is [Maven Compiler
Plugin|http://maven.apache.org/plugins/maven-compiler-plugin/xref/org/apache/maven/plugin/compiler/AbstractCompilerMojo.html#420]
where you can choose a compiler by its id. Implementations are marked as a
Component and can be chosen by the hint.
- through Plexus Configuration. I couldn't find a good example, but it should
be something like this:
{code:xml}
<configuration>
<versionPolicyManager
implementation="com.acme.custom.MyVersionPolicyManager">
</versionPolicyManager>
</configuration>
{code}
The advantage of the latter is that it is very straightforward if you want to
use additional fields/setters on your VersionPolicyManager. For that reason
this would be my choice right now.
> 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
