[
https://issues.apache.org/jira/browse/HADOOP-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823162#comment-13823162
]
Colin Patrick McCabe commented on HADOOP-9991:
----------------------------------------------
Thanks for taking a look at this task. It's a difficult one.
One thing I'd like to add is that we now have httpcore-4.2.5 in trunk combined
with httpclient-3.1. However, these two jars provide many of the same classes!
The reason is because the Apache httpclient library was end-of-lifed and
folded into the httpcore project.
I am concerned about this dependency since it seems like we should be including
one or the other, but not both (given that they provide some of the same
classes) I tried getting rid of httpclient 3.1, but it is not possible since
we use the custom URL class which is implemented there, and which was dropped
in httpcore (they advise using java.net.URI instead). Perhaps we could weed
out these uses of the custom URI and try dropping the old client?
> 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)
