[
https://issues.apache.org/jira/browse/HADOOP-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881691#action_12881691
]
Hemanth Yamijala commented on HADOOP-6800:
------------------------------------------
Tom, trying to see if I can review this, but I'm not very familiar with Ivy...
Is the goal of this jira to make sure that the versions for libraries we are
using in the 3 projects are the same ? I ask because there are a few libraries
with different versions in the common and mapreduce projects. For e.g.
commons-logging is 1.1.1 in common and 1.0.4 in mapred, and jets3t is 0.7.1 in
common and 0.6.1 in mapred. These don't seem to be excluded / modified in your
patch.
Would these need to be fixed too ?
Apologies if my understanding is completely wrong...
> 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
>
>
> 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.
