[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-community] version numbers and release qualifiers
|
Neither the semantic version spec or maven version compatibility rules
talks about case. The code for validation version compatibility in
maven always checks against the lower cased form of the string:
https://github.com/apache/maven/blob/45076f33a0f38e34c72f2493ae5be484f56466f1/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/ComparableVersion.java#L599
so implicitly the maven community uses case insensitive version
strings based on their code base. No one recommends using version
ranges, and I don't see the point of asking the entire maven community
their opinion on this issue. We just need to impose consistency. Red
Hat is fine with using the proposed upper case qualifiers given in the
original message.
On Tue, Jan 28, 2020 at 4:38 AM Werner Keil <werner.keil@xxxxxxxxx> wrote:
>
> In fact the Maven POM specification
> https://maven.apache.org/pom.html#Version_Order_Specification
> says nothing about the case of qualifiers.
>
> More importantly it even refers to "snapshot" in lower case, so at most these are examples, in reality the Maven and Apache community stick with upper case like "M1" while a few other qualifiers died with Maven2.
>
> The last time lower case ones like "alpha" got used by Maven plugins was roughly around the time of Maven2.
>
> Werner
>
> Werner Keil <werner.keil@xxxxxxxxx> schrieb am Di., 28. Jan. 2020, 08:36:
>>
