Hi,
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.
Matthias
Am 28.02.2025 um 12:10 schrieb Michael Osipov:
On 2025/02/28 08:28:22 "Piotr P. Karwasz" wrote:
Hi,
I saw that more and more Maven plugins are releasing 4.x betas, which
sounds like great news.
Might I, however, suggest the usage of pre-release qualifiers of the
form `beta.<n>` (with a dot) instead of `beta-<n>` (with a hyphen)? This
would improve compatibility between Maven ordering and the ordering
specified by the Semantic Versioning specification[1]. Maven doesn't
really care if the separator is a dot, hyphen or is omitted, but semver
expects numeric identifiers to be separated with a dot. Otherwise it
sorts lexicographically: `beta-1`, `beta-10`, `beta-2`.
Since I value consistency, I am proposing this change for plugins that
have not released a beta yet: it would be really strange if `beta-2` was
followed by `beta.3`.
We loosely follow SemVer, so do our parsers. Changing this would mean change
all versioning/release schemes. I bet that other committers would be reluctant
to that.
M
---------------------------------------------------------------------
To unsubscribe, e-mail:dev-unsubscr...@maven.apache.org
For additional commands, e-mail:dev-h...@maven.apache.org
