[HBASE-19422] using hadoop-profile property leads to confusing failures

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0, 1.3.2, 2.0.0-beta-1, 2.0.0, 1.2.7
• Assignee: Mike Drob
• Reporter: Ted Yu
• Created: 04/Dec/17 21:50
• Updated: 01/Aug/18 06:20
• Resolved: 05/Dec/17 19:09

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.

Issue Links

• is related to: HBASE-18942 hbase-hadoop2-compat module ignores hadoop-3 profile