I seem to recall discussing this recently, I think the behaviour is currently undefined. We will improve this in 2.1 with better conflict resolvers, but you can always force a version and/or scope in your current pom.
- Brett On 10/27/05, Donszelmann, Mark <[EMAIL PROTECTED]> wrote: > Hi > > I see the following problem in Maven 2.0: > > I have a artifact A, which depends compile scope on B, and test scope on C. > B and C depend compile scope on D. > > When I run mvn one of the following cases happens: > > 1. > > A gets selected for compile > B gets selected for compile > D gets selected for compile > C gets selected for test > > compilation succeeds. > > 2. > > A gets selected for test > B gets selected for test > D gets selected for test > C gets selected for test > > followed by > > A gets selected for compile > B gets selected for compile > (but D does not get selected for compile) > > compilation fails on any reference to classes from artifact D. > > > Maven chooses case 1 or 2 depending on the time of the day... > I have around 10 artifacts of this case in a multi-module and always > one or two do not compile, and not always the same. > > Anybody seen this, is this a known problem. > > Regards > Mark Donszelmann > > > --------------------------------------------------------------------- > 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]
