[
https://issues.apache.org/jira/browse/HADOOP-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822267#comment-13822267
]
Steve Loughran commented on HADOOP-9991:
----------------------------------------
Stack, HBase's needs are one of the things I'm thinking of, and once you get
into the goal of including Hadoop, HBase and accumulo into a project, things
get worse to the extent I couldn't even pull in htmlunit:
[https://github.com/hortonworks/hoya/blob/master/pom.xml]
# We should really add ZK and avro into the mix here too
# I'd love to see stripped down clients -which we could address by having some
lean poms that only include the core bits to talk to localfs, hdfs, yarn, MR,
all optional client-side bits (avro integration, ftpfs, s3fs, pulled to the
side where you can add them if you explicitly want/need them). Yes, this adds
more POMs, but downstream it'll be better
# I'd like a lot of the cleanup into 2.3
> 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)
