I see your point. What I ended up doing is converting my version ranges to [3.2.0-!, 4.4.0]. This seems to be working properly. Can you think of anything that might break after I have done this?
Roshan -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 23, 2007 2:30 PM To: Maven Users List Subject: Re: Version Range Question Per the "Dependency Mediation and Conflict Resolution" wiki page, this is the correct behavior... http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict +Resolution Default Version comparison definition The default specification should be composed as follows: <major>.<minor>.<revision>([ -<qualififer> ] | [ -<build> ]) For ordering, the following is done in order until an element is found that are not equal: ...if qualifier does not exist, it is newer than if it does ... Wayne On 10/23/07, Roshan A. Punnoose <[EMAIL PROTECTED]> wrote: > Hi, > > > > With version ranges, I am finding that if I have a version range of > [3.3.0, 4.4.0], it will not pick up my dependency with version > 3.3.0-2007. Basically it is saying that 3.3.0-2007 is < 3.3.0. Any > ideas? > > > > Roshan > > --------------------------------------------------------------------- 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]
