[
https://issues.apache.org/jira/browse/HBASE-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238967#comment-16238967
]
Jan Hentschel commented on HBASE-19076:
---------------------------------------
Where do you get the failure mentioned in the description? When running mvn
clean install against the current master the enforcer rule passes.
> Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
> --------------------------------------------------------------------
>
> Key: HBASE-19076
> URL: https://issues.apache.org/jira/browse/HBASE-19076
> Project: HBase
> Issue Type: Bug
> Components: dependencies
> Affects Versions: 3.0.0
> Reporter: Qilin Cao
> Assignee: Qilin Cao
> Priority: Major
> Attachments: HBASE-19076.patch
>
>
> After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
> with the hbase-error-prone module.
> {code}
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) @ hbase-error-prone ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
> hbase-error-prone ---
> [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
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
