[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] version numbers and release qualifiers
|
Yes, Piotr, thanks for the pointer! More than we ever wanted to
know about Maven versions. :-)
I note that that document uses lower case version qualifiers, but in
fact Maven ignores case when comparing version qualifiers. I
haven't tried deploying a "-snapshot" release to see if that works
as expected.
Does the use of lower case in this document influence our choice of
lower case vs. upper case for qualifiers? I assume not.
It's also interesting that this document implies that "b" is short
for "beta", even though I think we've been using it as short for
"build", which has completely different semantics, although it
probably works out to be about the same in practice.
Kevin Sutter wrote on 1/17/20 12:26 PM:
+1, Piotr. I
was just going to post the same thing. Thanks for the write-up!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
"Piotr
Żygieło" <piotr@xxxxxxxxxx>
To:
jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date:
01/17/2020
01:05
Subject:
[EXTERNAL]
Re: [jakartaee-platform-dev] version numbers and release
qualifiers
Sent
by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
Hi Markus
> Maven is able to find latest builds (i. e. 1.1.1-2 is a
later build
than 1.1.1-1) only if the build is all-numbers.
I don't think that's true.
> Using ranges like [1.0; 1.1) will care for that build
numbers, IMHO
not only for the major, minor and patch numbers.
> Maven cannot do that if there is a letter in the build
number, because
it treats that as a non-buildnumber but as a "qualifier"
> (See Maven Version Syntax description). "qualifiers" are
not necessarily integral.
I'm pretty sure that info is not complete. Can you link to
"Maven
Version Syntax" you mentioned?
Per [1]:
>> Non-numeric ("qualifiers") tokens have the
alphabetical
order, except for the following tokens which come first in
this order:
>> "alpha" < "beta" < "milestone"
< "rc" = "cr" < "snapshot" < ""
= "final" = "ga" < "sp"
> For example Maven has no clue if -rc1 is later or earlier
that -rc01.
as 1 == 01 they are the same.
However there is that special case for "b" qualifier (which is
alias
for "beta") also used by discussed [2] in different role.
1. https://maven.apache.org/pom.html#Version_Order_Specification to
see that qualifiers _are_ taken into consideration
2. https://wiki.eclipse.org/JakartaEE_Maven_Versioning_Rules
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
