mercury is the one you're after. Maven 3 will use Mercury 2009/8/19 Ed Hillmann <ed.hillm...@gmail.com>: > On Wed, Aug 19, 2009 at 3:55 PM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> >> The numbering scheme is only really important if you are using version >> ranges... >> >> If you are using version ranges, you really have to use Maven's >> scheme, or else ensure that String sorting works for your ranges. >> >> The versions-maven-plugin needs to know version numbering rules in >> order to decide whether versionA > versionB so it can tell you if >> there are newer versions available. >> >> The "mercury" and "numeric" schemes are both unbounded schemes, i.e. >> they can take as many digits as you can type... it is unlikely that >> you would want anything else. >> >> The main difference is between the two is that "mercury" has 'special' >> qualifiers and treats -'s as a lesser . while "numeric" only compares >> up to the first - as numbers, everything after the - is a qualifier >> (unless it is a number) and qualifiers are compared as strings. >> >> -Stephen >> >> > Thanks for the clarification. In the short term, I don't think we'll need > version range support for these artifacts (we're not expecting anything to > be using them in their POM file). However, it's good to know that we can > shift to something like numeric if in the future something depends on these > artifact with the 4-digit version number. > > Thanks again, > Ed >
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
