JavaFX after Java 23

5 views
Skip to first unread message

Graham Norris

unread,
Jun 29, 2026, 4:59:10 AMJun 29
to Polarbar Mailer
For Polarbar to continue to work in future, assuming it continues to use JavaFX, the following Java options will be required:

--enable-native-access=javafx.graphics --enable-native-access=javafx.media

If these are not present, Azul Java 24 and 25 will warn about the lack of them, and at some release after that, will fail instead.

Graham Norris

unread,
Jun 29, 2026, 5:46:48 AMJun 29
to Polarbar Mailer
... and if you use the WebKit Browser window stlye, you'll need --enable-native-access=javafx.web too.

Graham Norris

unread,
Jun 30, 2026, 6:47:50 AMJun 30
to Polarbar Mailer
It turns out you can more conveniently just use:
--enable-native-access=javafx.graphics,javafx.media,javafx.web

Or even:
--enable-native-access=ALL-UNNAMED

The latter could be placed in the manifest file when the Polarbar jar is built instead. It does, as might be expected, re-open use of native code to more than just the parts of JavaFX which need it.

Any of them can be placed in a JDK_JAVA_OPTIONS environment variable instead of on the command line (or manifest.)

Ref for all of this: https://openjdk.org/jeps/472
Reply all
Reply to author
Forward
0 new messages