On Sat, 2 May 2026 02:40:05 GMT, Christopher Schnick <[email protected]> wrote:
> This PR allows Main classes to be launched if they extend the Application > class, even when only having the JavaFX dependencies on the classpath instead > of the module path. This issue has been there for a long time and was quite > annoying for a lot of people: > https://stackoverflow.com/questions/78501081/how-do-i-fix-error-javafx-runtime-components-are-missing-and-are-required-to-r. > It is also a common use case for JavaFX developers when testing some PR to > create a quick reproducer class without setting up the module path properly. > > While it is true that launching modern JavaFX via the classpath is > unuspported, it still launches and prints its own warnings, which is better > than the previous behavior. The old launcher error message in this case is > misleading as the runtime components aren't really missing, they are just not > in the module path. > > This change should not have any change in behavior for any other case. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). This pull request has now been integrated. Changeset: f59ee5ac Author: Christopher Schnick <[email protected]> Committer: Alexey Ivanov <[email protected]> URL: https://git.openjdk.org/jdk/commit/f59ee5acfca6c0ac2cb60b892c4503bd0d18bd1a Stats: 8 lines in 1 file changed: 3 ins; 3 del; 2 mod 8248122: java launcher should launch normally if JavaFX modules not found Reviewed-by: kcr, prr, aivanov ------------- PR: https://git.openjdk.org/jdk/pull/31016
