Re: spring2 release number mess

On 01/09/2012 05:06 PM, David Walluck wrote:
> As far as other maven identifiers are concerned, replacing `-' by `_'
> should work in RPM, but for maven, 1.0-<identifier> is < 1.0, whereas in
> RPM it is > 1.0. What do to with `-' remains unclear (but, I would

Wait, this is not always the case with maven (cf.
<http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-project-dependencies.html#pom-relationships-sect-version-ranges>):

``If your version release number matches the format
<major>.<minor>.<incremental>-<qualifier> then your versions will be
compared properly; "1.2.3" will be evaluated as a more recent build than
"1.0.2", and the comparison will be made using the numeric values of the
major, minor, and incremental versions. If your version release number
does not fit the standard introduced in this section, then your versions
will be compared as strings; "1.0.1b" will be compared to "1.2.0b" using
a String comparison.''

These docs are bad! The use of the angle bracket indicates that all
components are necessary. It is hard to believe this is the case.
Moreover, doesn't maven handle the words `alpha' and `beta' differently?
According to this doc
<http://docs.codehaus.org/display/MAVEN/Versioning> it does, but again
this text also conflicts itself (the text above the table does not seem
to explain what is in the table).

Thanks maven doc authors!

In any case, I don't take back any of what I said about the RPM versioning.