I wish version ranges did/will get implemented the way it was first stated, or something similar/equivalent. As it is we had to abandon that feature altogether, we basically solved the problem by keeping everything as a snapshot until product release...so I mean 99% of the time we work with snapshots (and that's with hundreds of builds/devs). That actually works fairly well except now that maven3 requires timestamped snapshots that has caused lots of problems...still working through those.
-Dave On Mon, Sep 3, 2012 at 10:35 AM, Wayne Fay <[email protected]> wrote: >> Google leads me to this page: >> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution >> >> which states: >> Resolution of dependency ranges should not resolve to a snapshot >> (development version) unless it is included as an explicit boundary. > > I guess you missed this at the top of the page: > Dependency Mediation and Conflict Resolution > Skip to end of metadata > Added by Brett Porter, last edited by Carlos Sanchez on Jan 24, 2006 > This document describes the rest of the requirements for dependency > management that have not yet been implemented for Maven 2.0, > especially with regards to transitive dependencies. > > What you found there is not formal Maven documentation, but rather an > old discussion of how Maven should work. > > 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]
