Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-13994

explicitly declare the commons-lang3 dependency as 3.4

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0-alpha2, HADOOP-13345
    • Fix Version/s: HADOOP-13345
    • Component/s: build, fs/azure, fs/s3
    • Labels:
      None

      Description

      Other people aren't seeing this (yet?), but unless you explicitly exclude v 3.4 of commons-lang3 from the azure build (which HADOOP-13660 does), then the dependency declaration of commons-lang3 v 3.3.2 is creating a resolution conflict. That's a dependency only needed for the local dynamodb & tests.

      I propose to fix this in s3guard by explicitly declaring the version used in the tests to be that of the azure-storage one, excluding that you get for free. It doesn't impact anything shipped in production, but puts the hadoop build in control of what versions of commons-lang are coming in everywhere by way of the commons-config version declared in hadoop-common

        Attachments

        1. HADOOP-13994-HADOOP-13445-001.patch
          2 kB
          Steve Loughran
        2. HADOOP-13994-HADOOP-13345-001.patch
          2 kB
          Steve Loughran

          Issue Links

            Activity

              People

              • Assignee:
                stevel@apache.org Steve Loughran
                Reporter:
                stevel@apache.org Steve Loughran
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: