hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9991) Fix up Hadoop POMs, roll up JARs to latest versions
Date Wed, 16 Mar 2016 11:28:33 GMT

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

ASF GitHub Bot commented on HADOOP-9991:
----------------------------------------

Github user steveloughran commented on the pull request:

    https://github.com/apache/hadoop/pull/84#issuecomment-197274477
  
    Please can you file a separate JIRA for these two changes, link to HADOOP-9991 and include
justification. Version updates are a traumatic issue in Hadoop and done fairly reluctantly.
    
    FWIW, updating netty-all from beta to final makes sense just from a release perspective;
updating the other jetty less so 


> Fix up Hadoop POMs, 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.1.1-beta, 2.3.0
>            Reporter: Steve Loughran
>            Assignee: 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.3.4#6332)

Mime
View raw message