Good day to you, Beyer, Though I haven't experimented on it myself, you may want to play with the <classifier /> tag of the dependency elment ( see [1] ).
Cheers, Franz [1] http://maven.apache.org/ref/2.0.4/maven-model/maven.html#class_dependency Beyer,Nathan wrote: > > Given a set of versions for a JAR in a repo (1.0, 1.2, 2.0-alpha-1) and > a version range of [1, 2), should version 2.0-alpha-1 be picked? This > seems to be the state of affairs for Maven 2.0.4. > > I can understand why the algorithm is picking this, since 2.0-alpha-1 is > strictly less than 2, but this seems rather undesirable, at least to me. > Does anyone else see this as incorrect? If this is correct, is there any > version range syntax to avoid this? How would I express anything with a > major version of 1 starting at 1.0? > > -Nathan > > > ----------------------------------------- > CONFIDENTIALITY NOTICE This message and any included attachments > are from Cerner Corporation and are intended only for the > addressee. The information contained in this message is > confidential and may constitute inside or non-public information > under international, federal, or state securities laws. > Unauthorized forwarding, printing, copying, distribution, or use of > such information is strictly prohibited and may be unlawful. If you > are not the addressee, please promptly delete this message and > notify the sender of the delivery error by e-mail or you may call > Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) > (816)221-1024. ------------------------------------------- > -- View this message in context: http://www.nabble.com/-m2--Version-ranges-and-qualifiers-tf2887797s177.html#a8074137 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
