Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 1.0-rc3
-
Fix Version/s: None
-
Component/s: core
-
Labels:None
-
Environment:WinXp
Description
Example:
<dependency>
<groupId>displaytag</groupId>
<artifactId>displaytag</artifactId>
<version>1.0-rc1</version>
<jar>displaytag-1.0-rc1.jar</jar>
<url>http://displaytag.sourceforge.net/</url>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>
<dependency>
<groupId>displaytag</groupId>
<artifactId>displaytag</artifactId>
<version>12</version>
<jar>displaytag-12.tld</jar>
<type>tld</type>
<url>http://displaytag.sourceforge.net/</url>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>
Maven will download and integrate the first dependency, however it skips the second one thinking it is the same, even tho its version, jar name, and type are entirely different. It displays the same behavior if I omit the jar tag as well. (And the jar tag should likely be renamed since it could be something different than a jar, especially in this case).
Issue Links
- duplicates
-
MAVEN-1087
Dependency type should participate in equals() and hashcode()
-
- is duplicated by
-
MAVEN-1418
A later dependency in project.xml with same name, different type is ignored
-