Hi,
On 28.02.2025 20:07, Matthias Bünger wrote:
and we loosely follow / recommend SemVer 1.0.0
https://maven.apache.org/guides/mini/guide-naming-conventions.html
and there (https://semver.org/spec/v1.0.0.html) its listed
>>
A pre-release version number MAY be denoted by appending an arbitrary
string immediately following the patch version and a dash. The string
MUST be comprised of only alphanumerics plus dash [0-9A-Za-z-].
Pre-release versions satisfy but have a lower precedence than the
associated normal version. Precedence SHOULD be determined by
lexicographic ASCII sort order. For instance: 1.0.0-alpha1 < 1.0.0-beta1
< 1.0.0-beta2 < 1.0.0-rc1 < 1.0.0.
Thanks, that explains why dot `.` can not be used as a separator. Would
you consider switching to SemVer 2.0.0 and dots? This would align the
way ComparableVersion[1] and SemVer sorts versions:
* 1.0.0-beta-2 < 1.0.0-beta-10 and 1.0.0-beta.1 < 1.0.0-beta.10
according to ComparableVersion.
* 1.0.0-beta-2 > 1.0.0-beta-10, but 1.0.0-beta.2 < 1.0.0-beta.10
according to SemVer 2.0.0
Note: this is mostly a curiosity for me. Even if the Version Range
Spec[2] were to define a `semver` versioning, I would never use anything
other than `maven` for Java dependencies.
Piotr
[1]
https://maven.apache.org/ref/current/maven-artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html
[2]
https://github.com/package-url/purl-spec/blob/main/VERSION-RANGE-SPEC.rst
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
