hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6800) Harmonize JAR library versions
Date Sat, 26 Jun 2010 19:12:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882882#action_12882882
] 

Hemanth Yamijala commented on HADOOP-6800:
------------------------------------------

Tom, I tried again:

- Cleared Ivy cache - essentially did an rm -rf ~/.ivy2/cache
- On common, did ant veryclean jar mvn-install -- Here, I tried with and without -Dresolvers=internal
- On hdfs, did ant veryclean jar mvn-install -Dresolvers=internal. This step fails compilation,
with errors liks : 
org.apache.hadoop.hdfs.server.namenode.NameNode is not abstract and does not override abstract
method refreshSuperUserGroupsConfiguration(org.apache.hadoop.conf.Configuration) in org.apache.hadoop.security.RefreshUserMappingsProtocol

These errors do not come when I build the projects without the mvn-install option. Is there
anything I'm doing incorrectly ?

Also, please note that of the two sets of duplicates I mentioned, one set is in the ivy configuration
we're defining. So, in HDFS proxy's ivy/libraries.properties, we say junit.version=3.8.2 whereas
in hdfs core, we say this is 4.8.1. Similarly for other libraries mentioned in ivy-declarations.dump.merged.
Shouldn't this be resolved ?

> 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.


Mime
View raw message