These are 2 separate issues. As long as the bugfix/patch-part contains
non-numeric values and Maven (actually Aether) still does a String match
(apart from those special cases like alpha, beta, RC) we have to be very
careful with calculating the next version.
You could question if this kind of logic belongs in the
maven-release-plugin, since it is more related to how Maven resolves
versions.
Robert
Op Tue, 13 Nov 2012 22:22:48 +0100 schreef Manfred Moser
<manf...@mosabuam.com>:
On Tue, November 13, 2012 12:38 pm, Jason van Zyl wrote:
This is a long-standing issue, but I think a document and standard has
emerged that I think is reasonable. How do people feel about trying to
adhere to:
http://semver.org
and moving toward using this as our standard versioning documentation?
I think that would be awesome. One of the things we would have to do is
fix the release plugin to work with 1.2.3-RC.2 as compared to 1.2.3-RC2.
Currently it does not correctly suggest the next version being 1.2.3-RC.3
but rather goes to 1.2.4-RC.2
This would also make it easier to explain the reasoning for the version
numbering since we could just point to the external docs as a best
practice.
manfred
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
