Re: JavaFX Phoebus warning at run time

["Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov>]

In short, it’s a warning that you can ignore.

 

In more detail, software tends to be split into what’s called  libraries or modules or packages or … depending on the programming language.

For Java, the basic unit has been and continues to be “jar” files (Java ARchive files, basically ZIP files).

That’s what we use.

From Java version 9 on, there is the new option of using “module” files. The maintainers of the JavaFX graphics library package their stuff in the form of a jar that can also be used as a module file, and as you can see from the warning, they suggest that everybody starts moving from jar to module files, but at this time I’m not sure there’s any advantage in doing that except for avoiding that warning. On the contrary, I’m quite sure that we rely on many libraries that are plain jars and not modules. While a pure module-based setup might at some point become a good idea because it adds some form of dependency hierarchy support, I don’t see right now as the best time to do that.

 

Cheers,

Kay

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of William F Badgett Jr via Tech-talk <tech-talk at aps.anl.gov>
Date: Monday, May 20, 2024 at 11:42 AM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: [EXTERNAL] JavaFX Phoebus warning at run time

When launching a locally build Phoebus 4.7.3 using JDK 21.0.3 on Alma Linux 9, we get a warning 

about JavaFX at Phoebus launch time:

 

2024-05-17 14:56:29 WARNING [javafx] Unsupported JavaFX configuration: classes were loaded from 'unnamed module @5e6622f5'

Is there a suggested remedy?

 

thanks

 

William Badgett

Accelerator Division Controls

Fermi National Accelerator Lab

Kirk and Wilson Roads, MS 360

BTE-214 Booster Tower East Room 214

Batavia, IL 60510 U.S.A.

badgett at fnal.gov