[jira] [Updated] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module

2018-01-11 Thread Jan Hentschel (JIRA) 

 [ 
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}

  com.google.errorprone
  error_prone_check_api
  ${error-prone.version}
  provided
  

  com.google.code.findbugs
  jsr305

  

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

[jira] [Updated] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module

2017-10-26 Thread Qilin Cao (JIRA) 

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

Qilin Cao updated HBASE-19076:
--
Priority: Major  (was: Blocker)

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

[jira] [Updated] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module

2017-10-23 Thread Qilin Cao (JIRA) 

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

Qilin Cao updated HBASE-19076:
--
Description: 
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}

  was:
After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures 
with the hbase-error-prone module.

{code}
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone ---
[INFO] Deleting 
/home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
[INFO] 
[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}


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

[jira] [Updated] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module

2017-10-23 Thread Qilin Cao (JIRA) 

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

Qilin Cao updated HBASE-19076:
--
Status: Patch Available  (was: Open)

> 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: Blocker
> 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-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone 
> ---
> [INFO] Deleting 
> /home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
> [INFO] 
> [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)

[jira] [Updated] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module

2017-10-23 Thread Qilin Cao (JIRA) 

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

Qilin Cao updated HBASE-19076:
--
Attachment: HBASE-19076.patch

submit a patch!

> 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: Blocker
> 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-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone 
> ---
> [INFO] Deleting 
> /home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
> [INFO] 
> [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)

[jira] [Updated] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module

2017-10-23 Thread Qilin Cao (JIRA) 

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

Qilin Cao updated HBASE-19076:
--
Description: 
After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures 
with the hbase-error-prone module.

{code}
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone ---
[INFO] Deleting 
/home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
[INFO] 
[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}

  was:
After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures 
with the hbase-error-prone module.

{panel:title=My title}
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone ---
[INFO] Deleting 
/home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
[INFO] 
[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.
{panel}


> 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: Blocker
>
> After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures 
> with the hbase-error-prone module.
> {code}
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone 
> ---
> [INFO] Deleting 
> /home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
> [INFO] 
> [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)