[ 
https://issues.apache.org/jira/browse/HADOOP-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hemanth Yamijala updated HADOOP-6800:
-------------------------------------

    Attachment: jars-in-lib.dump.merged
                ivy-declarations.dump.merged

Tom, I applied the latest patches for all three sub-projects, cleared my IVY 
cache, rebuilt all of them. Then, I compared the ivy library dependencies that 
we are declaring in the sources of the three packages and the libraries in the 
lib folder of the built packages. In both analyses, I still see some duplicate 
jars. I think most or all of the duplicates in source are coming from the HDFS 
Proxy ivy file. I don't know if this is reason why the libraries in the 
build/lib are ultimately repeating.

For e.g. here's a list of the jars in the ivy properties that have different 
versions:
commons-logging-api, commons-logging, ivy, jets3t, junit, mockito-all, 
slf4j-api, slf4j-log4j12

There are quite a few repetitions in the lib folders of the three packages:
ant,avro 
,commons-http-client,commons-lang,ivy,jackson-core-asl,jackson-mapper-asl,jetty,jetty-util,junit,paranamer,paranamer-ant,paranamer-generator,qdox,servlet-api,slf4j-api,slf4j-log4j12

I am attaching two text files that are the dumps of the ivy library 
declarations and the build/lib folder contents for your review.

Please note that I did not run the cluster with these packages - so things are 
possibly fine with these duplications as well.

> Harmonize JAR library versions
> ------------------------------
>
>                 Key: HADOOP-6800
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6800
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Tom White
>            Assignee: Tom White
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-6800.patch, HADOOP-6800.patch, HADOOP-6800.patch, 
> ivy-declarations.dump.merged, jars-in-lib.dump.merged
>
>
> Currently, multiple versions of the same library JAR are being pulled in for 
> various reasons.
> * Within the same project, multiple versions of the same JAR are pulled in. 
> E.g. Avro (used by Common) depends on Commons Lang 2.5 while Common depends 
> on Commons Lang 2.4.
> * Dependent subprojects use different versions. E.g. Common depends on Avro 
> 1.3.2 while MapReduce depends on 1.3.0. Since MapReduce depends on Common, 
> this has the potential to cause a problem at runtime.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to