[
https://issues.apache.org/jira/browse/HBASE-28261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797352#comment-17797352
]
Moran commented on HBASE-28261:
-------------------------------
Should we maintain consistency between hbase surefire. jdk11. flags and
bin/hbase? Currently, there seems to be no particularly good method to ensure
consistency. Perhaps we need some comments to remind the Committer and
contributors.
> Sync jvm11 module flags from hbase-surefire.jdk11.flags to bin/hbase
> --------------------------------------------------------------------
>
> Key: HBASE-28261
> URL: https://issues.apache.org/jira/browse/HBASE-28261
> Project: HBase
> Issue Type: Bug
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Trivial
>
> All the JDK11 seems to be coming from the runtime code, and we have found
> that the missing options are required for the runtime when testing JDK 17.
> Only the JDK17 "--add-opens java.base/jdk.internal.util.random=ALL-UNNAMED"
> is known to be used by the test code, and probably not by the runtime.
> Specifically, these ones are missing:
> java.base/java.io=ALL-UNNAMED (pending in HBASE-28259. If that one doesn't
> add it to surefire, we need to add that here)
> java.base/java.util=ALL-UNNAMED
> java.base/java.util.concurrent=ALL-UNNAMED
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
