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. 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. For example Maven has no clue if -rc1 is later or earlier that -rc01. -Markus Von: jakartaee-platform-dev-bounces@xxxxxxxxxxx [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Emily Jiang
Gesendet: Donnerstag, 16. Januar 2020 23:56
An: jakartaee-platform developer discussions
Betreff: Re: [jakartaee-platform-dev] version numbers and release qualifiers The format of x.x.y where x must be a number and y can contain letters, e.g. 2.0.3-RC1. What kind of version range do you use? if you use [2.0, 2.1). 2.0.3-RC1 will be in the range. Pleas stay compatible with Maven best practices. In particular, build
numbers must not have letters in Maven versions because they would break the
version range feature.
-Markus
-----Ursprüngliche Nachricht-----
Von: jakartaee-platform-dev-bounces@xxxxxxxxxxx
[mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Bill
Shannon
Gesendet: Mittwoch, 15. Januar 2020 22:30
An: jakartaee-platform developer discussions
Betreff: [jakartaee-platform-dev] version numbers and release qualifiers
I've updated our versioning spec [1] to reflect our recent decision to
use dot-dot version numbers for API jar files, e.g., of the form x.0.0.
Please let me know if you see any mistakes, especially in the OSGi rules.
Also, we need to decide what release qualifiers to recommend. So far
we've been recommending these (where <number> is a sequence number):
-b<number> - build
-m<number> - milestone
-rc<number> - release candidate
The pre-defined qualifier is "-SNAPSHOT", which raises the question as
to whether our qualifiers should be upper case as well. I've mostly
seen lower case being used, which is why the document recommends lower
case, but I can see an argument for all qualifiers being upper case.
Comments?
Once we come to a decision on this I'd like to send it to the PMC and
ask them to "bless" it as the recommendation for all EE4J and Jakarta EE
projects.
Thanks.
[1] 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
--
|
