Suggestion: Move parts using JavaFX into separate deployment units

[Ben Hermann]

When using parts of the OPAL framework (e.g. OPAL-Developer Tools) in a library fashion users are forced to use a JRE including JavaFX (such as the Oracle one). In a standard Debian installation (i.e. most server/docker scenarios) users typically use OpenJDK which does not contain JavaFX. There is an open version of JavaFX available that is sufficient for running OPAL, however, it is making deployments unnecessarily large as no graphical user interface is used. I suggest to separate the parts of the core functionality and the parts the are handling the GUI into separately deployable components (i.e. JAR files here). This would allow for more focussed deployment and smaller images.

[Michael Eichberg]

Hi, do you talk about splitting up "Hermes" in two parts?

[Ben Hermann]

Yes... But I was unsure what other parts may use JavaFX as well.

[florian_kuebler]

This should be fixed