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

Hudson commented on HBASE-26916:
--------------------------------

Results for branch master
        [build #556 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/556/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/556/General_20Nightly_20Build_20Report/]






(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/556/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/556/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 source release artifact{color}
-- See build output for details.


(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console 
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/556//console].


> Fix missing braces warnings in DefaultVisibilityExpressionResolver
> ------------------------------------------------------------------
>
>                 Key: HBASE-26916
>                 URL: https://issues.apache.org/jira/browse/HBASE-26916
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-3, 2.4.12
>
>
> It will cause incorrent indentation warnings, like this
> {code}
>       if (connection != null) try {
>         connection.close();
>       } catch (IOException ioe) {
>         LOG.warn("Failed close of temporary connection", ioe);
>       }
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to