write a test to ensure duplicate libraries are not pulled in

lipinggm / tlb

Automatically exported from code.google.com/p/tlb

0 stars 0 forks source link

write a test to ensure duplicate libraries are not pulled in #64

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

we had both commons-codec 1.2 and 1.4 in core dependencies, we pulled in 1.2, 
ivy pulled 1.4 as a dependency of some other library. we need a test guarding 
such duplication.

Original issue reported on code.google.com by singh.janmejay on 3 Mar 2011 at 11:43

GoogleCodeExporter commented 9 years ago

Original comment by itspa...@gmail.com on 17 Mar 2011 at 8:23

Added labels: Milestone-0.4

GoogleCodeExporter commented 9 years ago

Original comment by itspa...@gmail.com on 20 Nov 2011 at 7:25

GoogleCodeExporter commented 9 years ago

Original comment by singh.janmejay on 9 Jan 2012 at 12:34

Changed state: Started

GoogleCodeExporter commented 9 years ago

Fixed in 3ab6fd4a47d234e75af5c394f7955055255d9607 (tlb repo).

It works using a custom task, both one-jar bundling and java-dependencies 
preparing targets call it to validate the directory that contains a flat list 
of all dependency jars doesn't have any duplicates.

Original comment by singh.janmejay on 13 Jan 2012 at 1:43

Changed state: Fixed