Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] version numbers and release qualifiers
No and of course some of the other vendors that not only because they pay sometimes higher fees, but also because they have a large customer base also voiced their practices and preferences, so it isn't just individuals like us.

Werner


On Wed, Jan 29, 2020 at 7:59 PM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

At least in my real world projects I do have tons of dependencies in my POMs, mostly non-Jakarta, hence all having different kinds of version syntax, and I had no problem with that ever. The case that someone REALLY has a problem with that is purely academic. Do all your customers really ONLY use Jakarta EE dependencies, or how do they deal with the fact that they need a non-Jakarta EE dependency and that one uses a different case… ? Come on, this argument is not meant serous, right? ;-)

 

This discussion started because Bill wanted to get opinions. You have yours, I have mine. Now Bill knows them. Now he may deal with that in any way he wants. Don't see a need to further drive this thread, do you?

 

-Markus

 

 

Von: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] Im Auftrag von Werner Keil
Gesendet: Mittwoch, 29. Januar 2020 19:49
An: Jakarta EE community discussions
Betreff: Re: [jakarta.ee-community] version numbers and release qualifiers

 

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

_______________________________________________
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

Back to the top