Skip to content

[MNG-8241] Specify handling of comparison between numeric and non-numeric characters #661

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
elharo merged 5 commits into from
Feb 15, 2025
Merged

[MNG-8241] Specify handling of comparison between numeric and non-numeric characters #661

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a13d82c
[MNG-8241] Specify handling of numeric and non-numerioc tokens
elharo Feb 3, 2025
51e4c74
More examples
elharo Feb 4, 2025
f540bf3
Avoid non-ASCII characters.
elharo Feb 4, 2025
7151db6
Avoid non-ASCII characters.
elharo Feb 4, 2025
415bf7b
Update pom.apt.vm
elharo Feb 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 15 additions & 5 deletions content/apt/pom.apt.vm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -357,7 +357,7 @@ mvn install:install-file -Dfile=non-maven-proj.jar -DgroupId=some.group -Dartifa

**** Version Order Specification

If version strings are syntactically correct {{{https://semver.org/spec/v1.0.0.html}Semantic Versioning 1.0.0}}
If version strings are syntactically correct {{{https://semver.org/spec/v1.0.0.html}Semantic Versioning 1.0.0}}
version numbers, then in almost all cases version comparison follows the precedence rules outlined in that specification.
These versions are the commonly encountered alphanumeric ASCII strings such as 2.15.2-alpha.
More precisely, this is true if both version numbers to be compared match the "valid semver"
Expand All @@ -369,11 +369,11 @@ mvn install:install-file -Dfile=non-maven-proj.jar -DgroupId=some.group -Dartifa
plus sign or consider build identifiers.

When version strings do not follow semantic versioning, a more complex set of rules is required.
The Maven coordinate is split in tokens between dots ('<<<.>>>'), hyphens ('<<<->>>'), underscore ('<<<_>>>') and transitions between digits and characters.
The Maven coordinate is split into tokens between dots ('<<<.>>>'), hyphens ('<<<->>>'), underscores ('<<<_>>>'), and transitions between digits and characters.
The separator is recorded and will have effect on the order. A transition
between digits and characters is equivalent to a hyphen.
Empty tokens are replaced with "<<<0>>>". This gives a sequence of version numbers (numeric tokens) and version qualifiers (non-numeric tokens)
with "<<<.>>>" or "<<<->>>" prefixes. Versions are expected to start with numbers.
with "<<<.>>>" or "<<<->>>" prefixes. Versions are expected to start with ASCII digits.

Splitting and Replacing Examples:

Expand Down Expand Up @@ -411,14 +411,16 @@ mvn install:install-file -Dfile=non-maven-proj.jar -DgroupId=some.group -Dartifa

* if the prefix is the same, then compare the token:

* Numeric tokens have the natural order.
* Tokens comprised of the ASCII digits 0-9 (numeric tokens) have the natural order.

* Non-numeric tokens ("qualifiers") have the alphabetical order, except for the following tokens which come first in this order:
* Non-numeric tokens inlcuding non-ASCII digits ("qualifiers") have the alphabetical order, except for the following tokens which come first in this order:

"<<<alpha>>>" \< "<<<beta>>>" \< "<<<milestone>>>" \< "<<<rc>>>" = "<<<cr>>>" \< "<<<snapshot>>>" \< "" = "<<<final>>>" = "<<<ga>>>" \< "<<<sp>>>"

* the "<<<alpha>>>", "<<<beta>>>" and "<<<milestone>>>" qualifiers can respectively be shortened to "a", "b" and "m" when directly followed by a number.

* Alphabetic tokens other than the special cases described above come before numeric tokens.

* else "<<<.qualifier>>>" = "<<<-qualifier>>>" \< "<<<-number>>>" \< "<<<.number>>>"

* <<<alpha>>> = <<<a>>> < <<<beta>>> = <<<b>>> < <<<milestone>>> = <<<m>>> < <<<rc>>> = <<<cr>>> < <<<snapshot>>> < '<<<>>>' = <<<final>>> = <<<ga>>> = <<<release>>> \< <<<sp>>>
Expand All @@ -437,6 +439,8 @@ mvn install:install-file -Dfile=non-maven-proj.jar -DgroupId=some.group -Dartifa

* The usage of '<<<SP>>>' qualifier is discouraged. Increment the patch version instead.

* Avoid non-ASCII characters, including non-ASCII digits, which may sort in surprising ways.

[]

End Result Examples:
Expand All @@ -459,6 +463,12 @@ mvn install:install-file -Dfile=non-maven-proj.jar -DgroupId=some.group -Dartifa

* "<<<1-a1>>>" = "<<<1-alpha-1>>>"

* "<<<1.7>>>" \> "1.K"

* "<<5.zebra>>>" \> "5.aardvark"

* "<<1.α>>>" \> "1.b" (Note the Greek letter alpha.)

Note: Contrary to what was stated in some design documents, for version order, snapshots are not treated differently than releases or any other qualifier.

Note: As <<<2.0-rc1>>> \< <<<2.0>>>, the version requirement <<<[1.0,2.0)>>> excludes <<<2.0>>> but includes version <<<2.0-rc1>>>, which is contrary to
Expand Down