Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to IssueMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.9.0
    • 3.0.0-alpha4
    • build, fs/s3
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            aajisaka Akira Ajisaka Assign to me
            stevel@apache.org Steve Loughran
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment