my guess is that both jars will be downloaded but the first one will get the precedence because of the classpath
ideally, in a single project both A and B should use the same version.. why would we want to happen this? On Sun, May 25, 2008 at 7:58 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Maven uses a nearest first, but in the example you provided C is the same > depth. In this case it will go with the first version of C found, which is > dependent on if A or B is listed first in your pom. > > > On 5/25/08 7:05 AM, "Giovanni Azua" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I have tried researching these questions but I did not find any > > authoritative answer: > > > > 1) If via transitive dependency resolution there is a conflict found i.e. > > two dependencies use different versions of a fourth library, how does > maven > > resolves this? This is a.k.a. diamond problem: > > > > "My Project" > > | |-----> A ---> C (version 1.0) > > | > > |------------> B ---> C (version 1.1) > > > > If both C versions are pulled there will be runtime unpredictable > behavior. > > > > 2) If the point 1) is checked by Maven, how is it done? Using only > version > > numbers or md5sum? Is it possible enforcing the use of md5sum for this > > purpose? > > > > If you know where these questions are answered, pointing me to the > location > > will be most welcome! > > > > TIA, > > Best regards, > > Giovanni > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- cheers, - a
