Two dependencies with same group and artifactId, but different type, are thought to be the same

If, in the project.xml file of my project, I declare two different dependencies with the same groupId and artifactId, but different "type", maven thinks they're one and the same and only downloads and processes the first of them.

As an example (these can be found at ibiblio.org/maven):

<dependency>
<groupId>struts-menu</groupId>
<artifactId>struts-menu</artifactId>
<version>2.3</version>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>

<dependency>
<groupId>struts-menu</groupId>
<artifactId>struts-menu</artifactId>
<version>1.2</version>
<type>tld</type>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>

This avoids a correct use of maven in cases like the one above, where we have a web tool library and an associated tld. In this case maven will download the struts-menu-2.3.jar file (and include it in the war) and ignore completely the struts-menu-1.2.tld file.