You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2019/03/03 12:35:00 UTC

[jira] [Commented] (HBASE-21895) Take more care on the error prone plugin and warnings

    [ https://issues.apache.org/jira/browse/HBASE-21895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782715#comment-16782715 ] 

Duo Zhang commented on HBASE-21895:
-----------------------------------

OK, seems not easy. I do not know why we use such a complicated way to integrate error prone...

If we want to add new checks, can we use a separated repo instead of doing this magic in the main hbase repo? What do you think sir [~apurtell]? Thanks...

> Take more care on the error prone plugin and warnings
> -----------------------------------------------------
>
>                 Key: HBASE-21895
>                 URL: https://issues.apache.org/jira/browse/HBASE-21895
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: Duo Zhang
>            Priority: Major
>
> As shown in HBASE-21890 , the error prone warnings are truly useful.
> But now, the javac warnings section in the pre commit result is messed up, it always reports unrelated warnings. Need to take a look at it.
> And also, we should try out best to clean up the warnings.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)