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. |