From the spec:
A version string is a series of positive numbers separated by periods. The numbers are compared component by component from left to right. If any number is greater than the corresponding number of the supplied string the method returns true. If the number is less than it returns false. If the corresponding numbers are equal the next number is examined. That shouldn't be a problem... On 12/19/06, ir. ing. Jan Dockx <[EMAIL PROTECTED]> wrote:
I believe that Maven version number support should at least make it possible to apply the specification / implementation version numbering scheme that is part of the Java standard (<http:// java.sun.com/j2se/1.5.0/docs/guide/versioning/spec/ versioning2.html#wp89936>). On 19 Dec 2006, at 9:33, [EMAIL PROTECTED] wrote: > Jason Dillon <[EMAIL PROTECTED]> schrieb am 19.12.2006 01:26:54: > >> I've seen projects switch back and forth... depends on who is in >> power at the time and what style they like. So it would be best if >> mvn would be able comprehend: > > Since versions are such an important information in Maven, Maven > should > refuse version numbers which aren't easily comparable. > > How about forcing the contents of the version element in the POM to > 1-3 > digits, separated by dots? That would "help" people who can't decide. > > After that, you can add something with "-" which maven will just > string-compare (so alpha10 comes between alpha1 and alpha2). > > Regards, > > -- > Aaron Digulla > > --------------------------------------------------------------------- > 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]
