It's kinda a bummber it isn't <major>.<minor>.<maint>.<build> or would only resort to string comparison when it encounters a "-".
-----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008 1:38 PM To: Maven Users List Subject: Re: specifying "latest" for a dependency > If you want anything greater than say 1.0.0.3 and anything less than > 1.0.0.99 you specify <version>(1.0.0.0,1.0.0.99)</version> you get > version 1.0.0.9 (even if there's a version 1.0.0.52). The (current and proposed future) versioning scheme is pretty well documented. [1] [2] Numerical version comparison only works for the first 3 dotted fields in the version. Once you get to 4 fields, the versioning reverts to "case-insensitive string comparison" for the qualifier. Thus: 2 > 1 1.5 > 1.4 1.1.1 > 1.1.0 1.0.0.9 > 1.0.0.52 [1] http://docs.codehaus.org/display/MAVEN/Versioning [2] http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict +Resolution Wayne --------------------------------------------------------------------- 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]
