>> On Sep 29, 2019, at 7:34 AM, Chuck Davis <cjgun...@gmail.com> wrote:
> ...
>
> P. S. It's really easy to develop with JFX (and getting better).
> Distribution/packaging is the kicker......having it in the JDK install was
> sweet.
That is the painful part. I suggested to the OpenJFX team that the jmods should
be hosted as Maven artifacts so they could easily be used in a build script to
produce the JRE image with jlink. Having to setup a JFX SDK to get them is
awkward when we have dependency management.
The other part is running and debugging - the native code needs to be available
at runtime but you can’t use a Jmod at runtime. Luckily the JavaFX jars will
try to extract the native libraries from the jars at runtime, but I wouldn’t
rely on that in production.
I’ve done Gradle scripts to grab JavaFx jmod files from my local Artifactory
server, use jlink to produce a JRE, and run/debug with that JRE as well as use
it with the jpackage EA to produce installers. It’s all a bit sloppy, but it
works.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
