Posted by jonbarril on Sep 27, 2023; 8:52pm
URL: https://forum.jogamp.org/Unable-to-determine-GraphicsConfiguration-tp4042444p4043000.html

I am building an executable jar. It used to work fine. I recently tried building it and it failed. I updated the jogl libs and that fixed a known problem with earlier versions, but now I get the "Unable to determine GraphicsConfiguration" exception. Executing the jar with the VM args "--add-exports java.base/java.lang=ALL-UNNAMED --add-exports java.desktop/sun.awt=ALL-UNNAMED --add-exports java.desktop/sun.java2d=ALL-UNNAMED" works.

Why is this needed now? I don't understand the nature of the "problem" that this incantation solves. Is this a bug with java or with JOGL?

The people using the executable jar have enough technical knowledge to double-click the jar file to run it. Asking them to instead bring up a console to run it from command line with the magic VM parameters will be a stretch. My understanding is there is no way to include VM params in an executable jar. Is there any way around this?