hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9991) Fix up Hadoop Poms for enforced dependencies, roll up JARs to latest versions
Date Sun, 17 Nov 2013 15:17:22 GMT

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

Vinay commented on HADOOP-9991:
-------------------------------

Thanks Steve for initiating this major task.
Adding to above points, there are many duplicate jars in the distribution.
such as,
hdfs/lib, mapreduce/lib, tools/lib and yarn/lib  contains ~90% of the same jars present in
common/lib.

Is there any specific reason to keep these multiple copies of the jars.?

> Fix up Hadoop Poms for enforced dependencies, roll up JARs to latest versions
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-9991
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9991
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 2.3.0, 2.1.1-beta
>            Reporter: Steve Loughran
>         Attachments: hadoop-9991-v1.txt
>
>
> If you try using Hadoop downstream with a classpath shared with HBase and Accumulo, you
soon discover how messy the dependencies are.
> Hadoop's side of this problem is
> # not being up to date with some of the external releases of common JARs
> # not locking down/excluding inconsistent versions of artifacts provided down the dependency
graph



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message