Hello, My pom has a <dependencyManagement> set to configurre commons-collection dependency to version 3.2.
My eclipse classpath has the expected Jar, my build works fine. When I use assembly to create a jar-with-dependencies I get commons-collections-2.0 unpacked. I have 2 dependencies that both dependend on commons-collections with conflicting version. <dependencyManagement> is expected to solve this, but doesn't look to be used by assembly plugin. Is this a known bug ??? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
