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

Hudson commented on HADOOP-14118:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11315 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/11315/])
HADOOP-14118. move jets3t into a dependency on hadoop-aws JAR. (aajisaka: rev 
258342e76c87479db38a5404753ae91376a74299)
* (edit) hadoop-tools/hadoop-aws/pom.xml
* (edit) hadoop-common-project/hadoop-common/pom.xml
* (edit) hadoop-hdfs-project/hadoop-hdfs-httpfs/pom.xml
* (edit) hadoop-client-modules/hadoop-client/pom.xml
* (edit) hadoop-cloud-storage-project/hadoop-cloud-storage/pom.xml
* (edit) hadoop-common-project/hadoop-kms/pom.xml


> 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
>             Fix For: 3.0.0-alpha3
>
>         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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to