Yes. I think it was mng-1577 that made this intentional change. The dependencyManagement overrides the transitive versions. Dependency:analyze-dep-mgt can help you detect these conflicts later.
-----Original Message----- From: Benoit Decherf [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 12, 2008 11:21 AM To: Maven Users List Subject: dependencyManagement and conflicts Hi, I have 3 projects with their dependencies: * A |- B[1.0] |- C [1.1] * B |- C [1.0] * C So here there is a conflict in A for C, and this is what I'm expected: [INFO] Failed to resolve artifact. The artifact has no valid ranges test:C:jar:1.0 Path to dependency: 1) test:A:jar:1.0 2) test:B:jar:1.0 But now, if I define in A a dependencyManagement, I can force the verson of C and I don't have any warning about the conflict. Is this normal? Benoit --------------------------------------------------------------------- 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]
