Closed KlemenDEV closed 3 years ago
Known issue with Java 16 and 1.16.5, because securejarhandler accesses JDK internals which is now forbidden by default on Java 16 (on Java 9-15, it was set to warn only by default).
Solution is on the user side, by adding the --illegal-access=warn
command-line JVM argument on Java 16 at least. On Java 17 and higher, more refined JVM arguments -- --add-opens
, forcing open the required JDK modules to the securejarhandler module -- will replace that argument (as can be found in the Forge discord).
Note that in 1.17 Forge (as previewed in the discord), these refined JVM arguments are added by default on install to the profile/dedicated server.
I would also like to note that this is technically the invalid repository for this, as this is a Forge issue and not a ForgeGradle one.
I would also like to note that this is technically the invalid repository for this, as this is a Forge issue and not a ForgeGradle one.
My bad. I assume this is resolved then so I am closing this issue.
When running FG5 with J16 with 1.16.5 using runClient task, the launch fails with error: