hadoop-common-issues mailing list archives

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

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

Steve Loughran commented on HADOOP-9991:

Colin -that should be a separate JIRA

I'm trying to triage changes
# Low risk, no code changes
# minor code changes and/or medium risk
# major reworks and/or dependencies known to be brittle

the httpclient stuff is odd as it's actually been pretty reliable -and far better than the
java.net code. It's just that there are now two versions in there, which at least don't conflict.
What risks/harms is there from leaving it in, other than binary bloat & getting into the
classpath of downstream things -which as there aren't any later versions to conflict with,
shouldn't be more than an inconvenience downstream.

> 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

This message was sent by Atlassian JIRA

View raw message