[ https://issues.apache.org/jira/browse/HBASE-28261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799071#comment-17799071 ]
Istvan Toth commented on HBASE-28261: ------------------------------------- Technically, and we could probably write a a meven enforcer plugin script for this, but I still think that comments are sufficient. Hopefully this is mostly shaken out by now. > 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)