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

Hudson commented on HBASE-27870:
--------------------------------

Results for branch master
        [build #844 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/844/]: 
(/) *{color:green}+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/844/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/844/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/844/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Eliminate the 'WARNING: package jdk.internal.util.random not in java.base' 
> when running UTs with jdk11
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-27870
>                 URL: https://issues.apache.org/jira/browse/HBASE-27870
>             Project: HBase
>          Issue Type: Improvement
>          Components: build, pom, test
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.5, 2.4.18
>
>
> When fixing a jdk17 issue, we add a
> --add-opens java.base/jdk.internal.util.random=ALL-UNNAMED
> line in our pom when running UTs with jdk11+, so it will also be applied for 
> jdk11, but we only need this for jdk17, on jdk11, it will generate a warning, 
> as described in the title.
> We should try some maven magics to fix this.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to