Carsten Ziegeler opened MRELEASE-431 and commented

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 quite a lot of 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.

Affects: 2.0-beta-8

Attachments:

• 0001-MRELEASE-431-Configuration-of-policy-for-calculating.patch (17.36 kB)
• MRELEASE-431.patch (32.65 kB)
• MRELEASE-431-v2.patch (57.13 kB)
• MRELEASE-431-v3.patch (58.36 kB)

Issue Links:

• MRELEASE-797 support semantic versioning
  ("is duplicated by")
• MRELEASE-550 Version incrementation in non interactive release (batch-mode / -B)
  ("supercedes")
• MRELEASE-1078 Support version policy to read and use SCM tags and commits
  ("is depended upon by")
• MRELEASE-793 Release version hinting - stripping SNAPSHOT with unsupported versioning
  ("is depended upon by")

Remote Links:

• GitHub Pull Request #169
  

6 votes, 15 watchers