assembly doesn't honor dependencyManagement
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]
Re: assembly doesn't honor dependencyManagement
Exclude the commons-collection version that you don't want in your dependency declaration. http://maven.apache.org/pom.html#Exclusions HTH Jim On 9/26/07, nicolas de loof [EMAIL PROTECTED] wrote: 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]
Re: assembly doesn't honor dependencyManagement
There is many way to fix this, including using exclusions or simply declaring a new dependdency with expected version. I just want to know if I should log this in Jira as dependencyManagement is expected to avoid such version conflitcs. Nico. 2007/9/26, Jim Sellers [EMAIL PROTECTED]: Exclude the commons-collection version that you don't want in your dependency declaration. http://maven.apache.org/pom.html#Exclusions HTH Jim On 9/26/07, nicolas de loof [EMAIL PROTECTED] wrote: 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
