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-14118) move jets3t into a dependency on hadoop-aws JAR
Date Fri, 24 Feb 2017 21:00:45 GMT

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

Steve Loughran commented on HADOOP-14118:

ooh, you know in the cloud subprojects we're being pretty strict about certifying your test
runs: https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md

did you do one here? If not, as its a special case, I'll do it

> move jets3t into a dependency on hadoop-aws JAR
> -----------------------------------------------
>                 Key: HADOOP-14118
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14118
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: build, fs/s3
>    Affects Versions: 2.9.0
>            Reporter: Steve Loughran
>            Assignee: Akira Ajisaka
>         Attachments: HADOOP-14118.01.patch
> hadoop-common still declares a dependency on jets3t, which allows downstream projects
to pick it up. But as they can't get s3n to work without the hadoop-aws JAR, it's hard to
see how much use this is.
> I propose: moving it to a dependency of hadoop-aws JAR alone.
> Marking as incompatible as it will be in the specific situation
> * downstream maven build doesn't pull in hadoop-aws
> * command line doesnt have hadoop-aws JAR dependencies on CP and still wants to use jets3t.
Hard to imagine how this arises.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message