Re: [jakarta.ee-community] version numbers and release qualifiers

[Werner Keil <werner.keil@xxxxxxxxx>]

Ok so it's case-sensitive? (leaving aside some file systems especially on Windows aren't and you usually do find "4.13-rc-2" even if it's named "4.13-RC-2"  at least on an OS level)

That's a strong case for consistency, especially within a particular project or better the entire platform.

Maven may accept  "4.13-rc-2" > "4.13-RC-1" but if you try to download it or enter into your POM it does make a difference and a project that deviates from an otherwise consistent naming pattern would be quite error-prone.

Thanks,

Werner

On Wed, Jan 29, 2020 at 7:41 PM Piotr Żygieło <piotr@xxxxxxxxxx> wrote:

On Wed, 29 Jan 2020 at 19:20, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
>
> What actually do you mean with "deal"? Users can use any case they want, as Maven doesn't care at all.
>

Just for completeness.
Users have to use *exactly* the case used to release artifact, as
maven cares. For example, to depend on
https://repo.maven.apache.org/maven2/junit/junit/4.13-rc-2/, one has
to use version "4.13-rc-2". Up-cased "4.13-RC-2" version would not be
found.
Case is ignored for version ordering.

--
Piotrek
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community