[
https://issues.apache.org/jira/browse/HADOOP-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-6800:
------------------------------
Attachment: HADOOP-6800.patch
Thanks for taking a look, Hemanth. Yes, the goal is to make sure that the JAR
version used between the three projects are the same. My criterion for checking
this was to build the three tarballs, combine them, and visually check that
there were no conflicting versions in lib. This new set of patches corrects the
mismatches you saw (in some cases removing the variable since its not used in
the project).
> 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
>
>
> 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.
