Remove JavaFX JPMS enforcement
abhinay_agarwal at live.com
Fri Apr 24 13:19:57 UTC 2020
Hi Ty Young,
Thank you for reverting back.
Basic documentation has not changed since JavaFX 11.
Since it is difficult to keep up with the ever changing IDEs, we added a disclaimer on the top of each IDE section denoting the JavaFX and IDE version used for the tutorial.
And as always, in case you feel something can be improved, feel free to raise a PR .
GitHub - openjfx/openjfx-docs: Getting started guide for JavaFX 11<https://github.com/openjfx/openjfx-docs/>
Getting started guide for JavaFX 11. Contribute to openjfx/openjfx-docs development by creating an account on GitHub.
From: openjfx-dev <openjfx-dev-bounces at openjdk.java.net> on behalf of Ty Young <youngty1997 at gmail.com>
Sent: Friday, April 24, 2020 5:50 PM
To: openjfx-dev at openjdk.java.net <openjfx-dev at openjdk.java.net>
Subject: Re: Remove JavaFX JPMS enforcement
On 4/24/20 2:14 AM, Abhinay Agarwal wrote:
> Hi Ty Young,
> I am trying to identify which part of the documentation changed after
> JavaFX 13. The JVM arguments that you have specified are required
> since JavaFX 11. Alternatively, user doesn't need to pass these
> arguments if they are using javafx-maven-plugin to build and run the
> I might be missing something here. Can you be kind enough to point me
> to the specific issue and the related section in docs so that it can
> be fixed?
Right, so I think I got the issue sorted out.
TL;DR, you HAVE to use the archtype. Netbeans WILL NOT adjust its own
runtime "nbactions.xml" file if you decided to create a barebones
project and add JavaFX later, which is why runtime components are
missing and following the advice for Ant will fix the issue.
In Netbeans 12.3 Beta(what I'm using now) everything works.
In other words, as of Netbeans 12-3, **don't do this**:
New Project -> Java with Maven -> Java Application -> add JavaFX from
New Project -> Java with Maven -> Simple JavaFX Application Archtype(Gluon)
They changed the UI in Netbeans 12-3 beta, so the documentation will
need to be updated for it.
> Thanks in advance.
> -- Abhinay
> *From:* openjfx-dev <openjfx-dev-bounces at openjdk.java.net> on behalf
> of Ty Young <youngty1997 at gmail.com>
> *Sent:* Monday, April 20, 2020 10:07 PM
> *To:* openjfx-dev at openjdk.java.net <openjfx-dev at openjdk.java.net>
> *Subject:* Re: Remove JavaFX JPMS enforcement
> On 4/20/20 11:36 AM, Ty Young wrote:
> > On 4/20/20 10:47 AM, Mark Raynsford wrote:
> >> Am I missing something here? What absurd arguments are required for
> >> Maven projects?
> >> I have multiple applications here running in full module-path mode (the
> >> applications are modularized, and JavaFX is on the module path), using
> >> plain Maven builds with no special arguments, and IDEA as the IDE.
> >> This is on JDK 13, with the 13.0.2 JavaFX release from Central.
> > From the second warning on this page:
> > https://openjfx.io/openjfx-docs/
> > That's the absurd part. JavaFX 14 now requires this as a JVM runtime
> > argument:
> > --module-path /path/to/javafx-sdk-12/lib --add-modules
> > javafx.controls,javafx.fxml
> > Which wasn't required before. Not only is this a PITA and confusing
> > but it also prevents Maven from just handling everything. Netbeans
> > uses a custom file for runtime arguments, which the above is added to.
> Also, it gives JavaFX 12 as an example, which is wrong. It should be 14.
More information about the openjfx-dev