You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Akira Ajisaka (JIRA)" <ji...@apache.org> on 2017/02/24 19:14:44 UTC
[jira] [Updated] (HADOOP-14118) move jets3t into a dependency on
hadoop-aws JAR
[ https://issues.apache.org/jira/browse/HADOOP-14118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Akira Ajisaka updated HADOOP-14118:
-----------------------------------
Attachment: HADOOP-14118.01.patch
Attaching a patch
* Moved jets3t dependency from hadoop-common to hadoop-aws
* Removed exclusion of jets3t in hadoop-common dependency because jets3t dependency was removed from hadoop-common
> 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org