Remove JavaFX JPMS enforcement

[Ty Young]

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.