[
https://issues.apache.org/jira/browse/HBASE-21895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793792#comment-16793792
]
Andrew Purtell commented on HBASE-21895:
----------------------------------------
How would a separate repo work? What's the point of error-prone integration if
we can't run it on the code we are developing... which would be the main repo...
If error-prone integration is unstable then we have to decide if the work to
keep it working is worth the returns in the extra coverage it provides. It's a
valid choice to remove it. I remember some of the original motivation is we
would use it to implement our own static checks for various conventions and
invariants. This has not happened. So, in my opinion, much of its possibility
has been unrealized and its value is somewhat marginal.
> 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)
