+1 Scott. Thanks
for looking at the code, code never lies... :-)
I am also good
with the current proposal of using uppercase qualifiers. --------------------------------------------------- Kevin Sutter STSM, MicroProfile and Jakarta EE architect @ IBM e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
Stark <sstark@xxxxxxxxxx> To:
EE community discussions <jakarta.ee-community@xxxxxxxxxxx> Date:
Re: [jakarta.ee-community] version numbers and release qualifiers Sent
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: >>