On Sun, 16 Nov 2008 21:51:18 Dave Syer wrote: > > Hervé BOUTEMY wrote: > > > > [1] http://docs.codehaus.org/display/MAVEN/Versioning > > > > I didn't see any reference there to special qualifiers. But anyway, how > does it make sense for [1.0.0,2.0.0) (with an *exclusive* upper bound of > 2.0.0) to include anything from the 2.0.0. branch? I don't think users are > going to expect to pick up pre-production versions of 2.0.0 if they use that > as an upper exclusive bound.
Its really really obvious but somewhat anoyying... 2-SNAPHOT == 2.0.0-SNAPSHOT < 2.0.0 therefore ,2.0.0) is up to but not including 2.0.0 unfortunately including 2.0.0-SNAPSHOT but it makes sense, the only other option is to have a special case that not having a qualifier means 2.0.0-SNAPSHOT in a non-exclusive bound and thats just *arse* THE SOLUTION IS TO NEVER USE 2.0 just start at 2.1 and everything just works and makes sense... and why not use natural numbering anyway its more elegant... get rid of this odd development termininology of 0 versions. my 2c -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
