Java 11: Illegal reflective access ... to method com.sun.net.ssl.internal.ssl.Provider.isFIPS

This is observed when using WildFly 29 or 30 Beta1 on Java 11, e.g. in https://github.com/wildfly/wildfly-archetypes. Just build them ("mvn clean install"). During the build process, the "wildfly-getting-started-archetype" starts a managed server, and here this output is seen:

INFO: Starting container with: [C:\Temp\jdk-11.0.20\bin\java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -ea, -Djboss.home.dir=C:\Temp\wildfly-30.0.0.Beta1, --add-exports=java.desktop/sun.awt=ALL-UNNAMED, --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED, --add-exports=java.naming/com.sun.jndi.url.ldap=ALL-UNNAMED, --add-exports=java.naming/com.sun.jndi.url.ldaps=ALL-UNNAMED, --add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, --add-opens=java.base/java.lang=ALL-UNNAMED, --add-opens=java.base/java.lang.invoke=ALL-UNNAMED, --add-opens=java.base/java.lang.reflect=ALL-UNNAMED, --add-opens=java.base/java.io=ALL-UNNAMED, --add-opens=java.base/java.net=ALL-UNNAMED, --add-opens=java.base/java.security=ALL-UNNAMED, --add-opens=java.base/java.util=ALL-UNNAMED, --add-opens=java.base/java.util.concurrent=ALL-UNNAMED, --add-opens=java.management/javax.management=ALL-UNNAMED, --add-opens=java.naming/javax.naming=ALL-UNNAMED, --add-modules=java.se, -Djboss.home.dir=C:\Temp\wildfly-30.0.0.Beta1, -Djboss.server.base.dir=C:\Temp\wildfly-30.0.0.Beta1\standalone, -Djboss.server.log.dir=C:\Temp\wildfly-30.0.0.Beta1\standalone\log, -Djboss.server.config.dir=C:\Temp\wildfly-30.0.0.Beta1\standalone\configuration, -Dorg.jboss.boot.log.file=C:\Temp\wildfly-30.0.0.Beta1\standalone\log\server.log, -Dlogging.configuration=file:C:\Temp\wildfly-30.0.0.Beta1\standalone\configuration\logging.properties, -jar, C:\Temp\wildfly-30.0.0.Beta1\jboss-modules.jar, -mp, C:\Temp\wildfly-30.0.0.Beta1\modules, org.jboss.as.standalone]
Okt. 05, 2023 6:04:07 NACHM. org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 5.0.27.Final
Okt. 05, 2023 6:04:07 NACHM. org.xnio.Xnio <clinit>
INFO: XNIO version 3.8.9.Final
Okt. 05, 2023 6:04:07 NACHM. org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.8.9.Final
Okt. 05, 2023 6:04:07 NACHM. org.wildfly.security.Version <clinit>
INFO: ELY00001: WildFly Elytron version 2.2.2.Final
18:04:07,572 INFO [org.jboss.modules] (main) JBoss Modules version 2.1.2.Final
18:04:07,854 INFO [org.jboss.msc] (main) JBoss MSC version 1.5.1.Final
18:04:07,854 INFO [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
18:04:07,933 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 30.0.0.Beta1 (WildFly Core 22.0.0.Beta3) starting
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions (jar:file:/C:/Temp/wildfly-30.0.0.Beta1/modules/system/layers/base/org/wildfly/extension/elytron/main/wildfly-elytron-integration-22.0.0.Beta3.jar!/) to method com.sun.net.ssl.internal.ssl.Provider.isFIPS()
WARNING: Please consider reporting this to the maintainers of org.wildfly.extension.elytron.SSLDefinitions
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

It does not happen when running on Java 17.

See "common.bat" in WildFly bin directory: there is a check to add "java.base/com.sun.net.ssl.internal.ssl" to the JVM options only if the runtime contains this package.

As it does not happen with Java 17, I am not sure whether this is worth a fix.