[ 
https://issues.apache.org/jira/browse/HBASE-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Hentschel updated HBASE-19076:
----------------------------------
    Resolution: Cannot Reproduce
        Status: Resolved  (was: Patch Available)

Closing this one as not reproducible. I don't get this warning when running 
against the current master. JSR305 is explicitly excluded in the 
*error_prone_check_api* dependency.

{code:xml}
    <dependency>
      <groupId>com.google.errorprone</groupId>
      <artifactId>error_prone_check_api</artifactId>
      <version>${error-prone.version}</version>
      <scope>provided</scope>
      <exclusions>
        <exclusion>
          <groupId>com.google.code.findbugs</groupId>
          <artifactId>jsr305</artifactId>
        </exclusion>
      </exclusions>
    </dependency>
{code}

> 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
>         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)

Reply via email to