[MNG-2354] exclusion of a dependency prevents the dependency being added normally

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Component/s: Dependencies
• Assignee: Carlos Sanchez Gonzalez
• Reporter: Jorg Heymans
• Created: 08/Jun/06 08:56
• Updated: 06/Dec/06 12:08
• Resolved: 08/Jun/06 09:07

Description

Consider following usecase:

<dependency>
<groupId>commons-beanutils</groupId>
<artifactId>commons-beanutils-core</artifactId>
<version>1.7.0</version>
</dependency>
<dependency>
<groupId>commons-configuration</groupId>
<artifactId>commons-configuration</artifactId>
<version>1.2</version>
<exclusions>
<exclusion>
<artifactId>commons-beanutils-core</artifactId>
<groupId>commons-beanutils</groupId>
</exclusion>
</dependency>

Above pom configuration to me says: ignore the transitive dependency on commons-beanutils-core brought in by commons-configurations because i would like to define and use my own. However this configuration excludes commons-beanutils-core completely, eg in a war build it's not included as a dependency anymore.

Issue Links

• duplicates: MNG-1797 Dependency excludes apply to every subsequent dependency, not just the one it is declared under.