Hi Chris, It's actually "use nearest", rather than first found, which is basically the principle of you know better than your dependencies do what you need :)
1) is already possible if the place where you assume 3.8.1 is specified as [3.8.1], or perhaps [3.8,) 2) will be enabled in 2.1. It was on in the betas and without making it configurable it was a little hard to deal with and unfortauntely the configurable part missed the cut for 2.0. Cheers, Brett On 12/20/05, Chris Berry <[EMAIL PROTECTED]> wrote: > Greetings, > Yesterday I saw an issue w/ m2's dependency mediation. Some transitive > dependency wanted JUnit 3.7 and I'm assuming 3.8.1. Since this one was seen > first, it won. So, of course, my build broke. (Before you ask, I don't > directly declare the JUnit dependency in my POM because I have a "dependency > set" of commonly used dependencies ;-) > > I'm wondering about the status of a couple of "Mediators" > 1) A fail-fast-mediator would simply stop the build when conflicts occur. > IMHO, this would make the most sense as the default mediator since it makes > debugging a lot easier. No head scratching. > 2) A use-latest-mediator would be my choice. > > The use-first-found-mediator seems somewhat illogical to me?? > Thanks, > -- Chris > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
