Closed jzy3d closed 2 years ago
Running the JVM with
--add-exports java.base/java.lang=ALL-UNNAMED
--add-exports java.desktop/sun.awt=ALL-UNNAMED
--add-exports java.desktop/sun.java2d=ALL-UNNAMED
fixes the problem
I too get the exception. Using your fix (adding exports) fixes the problem. Why? Is there any way not to have to included these VM args?
I'm trying to build an executable jar for use by others, who can double-click the jar file but will likely not be able to deal with use of VM args and such.
With JOGL 2.4, Windows 10, Eclipse-provided JDK (17). Works with Azul JDK 8, 11.