exclusion of a dependency prevents the dependency being added normally

• Complexity:

  Intermediate

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.