The version "closest" to your project wins. In your case that would be module3.v1. http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html This is managed by Maven and you don't get any warnings.
However, you can always use some mojo like dependency:resolve to view the resolved dependencies. . Or even better/easier, use m2eclipse to view this in the pom editor. /Anders On Tue, Jun 22, 2010 at 15:25, Rüdiger Gubler (@work) <[email protected]>wrote: > > Hello, > > in which way resolve maven inherited dependencys. > E.G. module1.v1 -> depends module2.v1 and module3.v1 > module2.v1 -> depends module3.v2 > Which version of module3 is used and give maven a error or at least a > warning? > > Yours Rüdiger > > -- > View this message in context: > http://maven-users.828.n2.nabble.com/dependency-resolution-tp5208742p5208742.html > Sent from the maven users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
