[
https://issues.apache.org/jira/browse/HADOOP-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-6800:
------------------------------
Attachment: tar-munge
Hemanth, thanks for your persistence - I think we're getting close.
Is the ivy JAR repetition because there is a copy of both in the hdfs/ivy
directory? It's not a runtime dependency, so it's probably not a problem anyway.
The JSP one is because of the directory checked into hdfs/lib, which I think
can be deleted now.
Finally, here's the latest tar-munge I've been using, which doesn't suffer the
problem you describe.
> 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: build.sh, HADOOP-6800.patch, HADOOP-6800.patch,
> HADOOP-6800.patch, ivy-declarations.dump.merged, jars-in-lib.dump.merged,
> tar-munge
>
>
> 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.
