Its part of the spec.. sure.However only the Maven spec .. and different specs and tools might behave differently. The Maven repository format and related aspects are used by MANY more tools than just Maven.
Using the short version 2.1 causes issues such as mentioned earlier for no real benefit - so in the interest of making it more user friendly and explicit I advocate for just being explicit and using 2.1.0 Manfred Matt Foley wrote on 2020-01-08 12:36 (GMT -08:00): >>> So do NOT use a version like 2.1 .. instead use 2.1.0. > > The fact that 2.1 is identical to 2.1.0 is part of the spec, unambiguous, and > quite important for expected behavior IMHO. See "Trimming Examples" in > https://maven.apache.org/pom.html#Version_Order_Specification > <https://maven.apache.org/pom.html#Version_Order_Specification> > > Thanks, > —Matt > ————————— > Open Source Technologies @ > > > On Jan 7, 2020, at 1:29 PM, Manfred Moser <[email protected]> wrote: > > To be honest I dont think this needs fixing on the Maven side. If we change > behavior we just break other approaches. > > Instead users that want to use semver with three digits and want logic > ordering > should just do so. > > So do NOT use a version like 2.1 .. instead use 2.1.0. > > Problem solved. > > Also .. beyond the three digit semver usage .. dont assume anything beyond > purely alphanumeric sort to work. > > And of course dont ever do something like "latest", which is so popular in > other ecosystems like Docker or npm since you are just introducing a quicksand > scenario for your users. > E.g. latest release by date for example could be a patch release of an lower > version... > > manfred > > Elliotte Rusty Harold wrote on 2020-01-07 04:16 (GMT -08:00): > >> I've been looking at Maven 's version comparison algorithm: what it >> does, what it's documented to do, and what it should do. I ran a quick >> poll on my twitter feed to see what developers expect how version >> strings such as 2.1.q and 2.1 are compared. That is, what's the higher >> version? 2.1.q or 2.1? >> >> https://twitter.com/elharo/status/1213457533358223361 >> >> 2.1.q won in a landslide. This is, unfortunately, the opposite of what >> Maven currently assumes. See >> https://issues.apache.org/jira/browse/MNG-6420?focusedCommentId=17008025&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17008025 >> to understand how. >> >> This has real world consequences. xpp3:xpp3 for example uses letters >> with the expectation that 1.4.1.c comes after 1.4.1. There are >> probably other artifacts that use letters with these semantics too. >> >> I'm about 90% convinced this is something we should fix. It's a >> breaking change but I expect the high majority of devs who encounter >> this would classify the existing behavior as a bug. >> >> My main question is what version of Maven should we fix this in? >> 3.6.5? 3.7? 4.0? Thoughts? >> >> -- >> Elliotte Rusty Harold >> [email protected] >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
