Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-19422

using hadoop-profile property leads to confusing failures

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.4.0, 1.3.2, 2.0.0-beta-1, 2.0.0, 1.2.7
    • None
    • None

    Description

      When building master branch against hadoop 3 beta1,

      mvn clean install -Dhadoop-profile=3.0 -Dhadoop-three.version=3.0.0-beta1 -Dhadoop-two.version=3.0.0-beta1 -DskipTests
      

      I got:

      [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
      We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
      Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
      

      Here is part of the dependency tree showing the dependency:

      [INFO] org.apache.hbase:hbase-client:jar:3.0.0-SNAPSHOT
      ...
      [INFO] +- org.apache.hadoop:hadoop-auth:jar:3.0.0-beta1:compile
      ...
      [INFO] |  \- com.google.guava:guava:jar:11.0.2:compile
      [INFO] |     \- com.google.code.findbugs:jsr305:jar:1.3.9:compile
      

      We need to exclude jsr305 so that build succeed.

      Attachments

        1. HBASE-19422.patch
          1 kB
          Mike Drob
        2. 19422.v1.txt
          0.6 kB
          Ted Yu

        Issue Links

        Activity

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

          People

            mdrob Mike Drob
            yuzhihong@gmail.com Ted Yu
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment