Upgrading from OpenJFX 13 to a new version

This page is meant to document our upgrade process from OpenJFX 13.0.1 to another version - mainly so that we do not forget why we decided not to use certain versions.

Jfx@GSI 2021

During beamtime 2021 (R16) and on master/int, we used:

• OpenJDK 11
• OpenJFX 13.0.1
• ControlsFX 11.0.0

Jfx@GSI 2022

Beamtime 2022 (R17)

• OpenJDK 11
• OpenJFX 13.0.1
• ControlsFX 11.0.0
• RichTextFX 0.10.6
• TestFX OpenJFX Monocle jdk-12.0.1+2
• TestFX Junit 4.0.15-alpha

We have decided to keep using the same versions of JFX and ControlsFX as in the previous beamtime, as they are well-tested in our environment by now and we did not have time to properly evaluate new versions.

In 2023, we will probably be using OpenJDK 17.

On master/int

• OpenJDK 11 (asl75x: 11.0.13 , asl74x: 11.0.12)
• OpenJFX 17.0.2
• ControlsFX 11.1.0
• RichTextFX 0.10.6
• TestFX OpenJFX Monocle jdk-12.0.1+2
• TestFX Junit 4.0.15-alpha

Reasoning

• We decided not to use OpenJFX 16:
  • Our applications crash when we try to open the app console due to a bug in the WebEngine that was apparently not triggered in JFX 13, but is in 16: https://bugs.openjdk.java.net/browse/JDK-8264990
    • We could probably find a workaround for the app console (accsoft-gui-fx LogConsole - bug is triggered by LogConsoleSkin line 146 (call of webView.getEngine().load )), but we might run into problems with other components (possibly even from 3rd party libraries) that use the web view...
• We found a bug in OpenJFX 17 affecting ComboBoxes that causes one of our test cases to fail: https://bugs.openjdk.java.net/browse/JDK-8279140
  • This bug can be mitigated with a workaround that uses an otherwise unnecessary change listener. AW will implement this workaround for now.

-- AnnekeWalter - 11 Jan 2022