> This shouldn't happen if you're clean packaging. Not sure what you mean by "clean packaging". I can reproduce this problem with a simple "mvn clean install" run - both JAR versions end up in the WEB-INF/lib directory. The commons-xxx JARs are straight from the central repository.
> The default conflict resolution is nearest-wins, see MNG-612 for more > info. So as I understand it, it's not just the default, it's the *only* conflict resolution method (as of 2.0.x). > I'm currently working on some dependency diagnostic tools to be > included in the dependency plugin which should help track down these > types of problems. That would be quite helpful. I'd be happy to test it. OTOH, shouldn't it be simple to get a configurable warning (or even error) right from Maven's dependency handling code, without additional plugins? I think many people would find it useful if they could set Maven to "strict mode" to throw an error if there isn't 100% convergence. Thanks, Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
