[
https://issues.apache.org/jira/browse/HADOOP-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883145#action_12883145
]
Hemanth Yamijala commented on HADOOP-6800:
------------------------------------------
Tom, I've been able to get a single node cluster up and run basic tests - hdfs
and map/reduce jobs. Things appear to work fine.
Regarding the ivy JAR, I don't see this now, so maybe there was a problem in my
previous run. I think you are right about the jsp-2.1.jar. So, are you planning
to delete this in this set of patches ?
Lastly, since we've changed some of the contrib libraries, should we give a
heads up - maybe on the *-dev mailing lists asking folks to take a look at the
patches ?
> 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.
