On 12/8/06, Nigel Magnay <[EMAIL PROTECTED]> wrote:
I think this is a bug in surefire. If I run my project with mvn -X I see in the output :
...
[DEBUG] commons-logging:commons-logging:jar:1.0:compile (removed - nearer found: 1.0.4)
...
However, the version of commons-logging that appears in my classpath for test is 1.0.4, NOT 1.1 as it appears that it ought to be. Additionally, this means that avalon-framework is not present in my surefire test classpath, causing tests to break.
If "removed - nearer found: 1.0.4" is the last thing you see, then that's the version Maven has chosen. The list archives contain plenty of discussion about Maven 2.0.4's approach to transitive dependency resolution, especially when <dependencyManagement> is in use. It's something that has been improved for the next release. The usual fix is the explicitly declare the dependency version you want, in the project pom where the problem is occurring. If that doesn't help, we need to see the pom and the full output of mvn -X. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
