> 2009/6/14 B Smith-Mannschott <[email protected]>: >> On Sat, Jun 13, 2009 at 22:56, Jim Sellers<[email protected]> wrote: >>> I assume that maven treats them as Strings internally, not doubles. >>> >>> Just like version 3.0-RC1 and 1.0.3-beta3 are valid versions. >>> >> >> Doubles!? How would you make a double out of 2.0.0? Nonsensical. >> >> http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-pom-syntax.html >> >> Maven version numbers generally have this form: >> >> <major version>.<minor version>.<incremental version>-<qualifier> >> >> The version parts are treated as integers. Missing numeric parts are >> considered zero. The qualifier is compared as a string. Any version >> not following this syntax is treated purely as a string. >> >> I don't recall if unparseable versions always sort before or always >> after parseable version numbers. It's been a while since I read the >> code that actually takes care of this. It made me throw up a little >> inside. >> >> // ben
On Sun, Jun 14, 2009 at 19:25, Stephen Connolly<[email protected]> wrote: > however 2.0 and 2.0.0 are both parseable versions. > True, and they should be equivalent. Indeed the OP's second post demonstrates this. So, whatever the explanation for the OP's issue, it's not that parsing and comparision of versions is somehow mysteriously broken. // ben --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
