Chris,
The reason I mentioned JavaFX as problematic is that it is not included JDK
releases beyond 1.8. The JavaFX deploy capability is the basis for NetBeans
native packaging. Thus the Netbeans packaging fails if NetBeans is run on a
later version of Java than 1.8. As you probably surely know, JavaFX has moved
to https://openjfx.io/ and also see
https://gluonhq.com/services/javafx-support/ . As far as I can see (correct me
if I'm wrong) JavaFX 14.0.1 sdk no longer provides
com.sun.javafx.tools.ant.FXJar and NetBeans native packaging fails. Hence (and
only for this reason) I labelled the use of JavaFX as problematic for
deployment. The packaging code seems to have been extracted from JavaFX to
form javapackager which then became jpackage in JDK14. In my experience,
jpackage has fewer challenges in that I could get it to work more or less first
time. Be aware however that it is in "incubator" stage of its lifecycle.
Hopefully it will become a standard Java component that we can rely on going
forward.
Regards
David
On 28/05/2020, 15:57, "Chris Olsen" <col...@mchsi.com> wrote:
David and All --
Having recently struggled through jpackage on both PCs and Macs, Netbeans
support would be (IMHO) fantastic! If I were a developer, rather than a
statistician writing software for my students' use, I would most certainly
offer to assist. Now, however, I have an amateur's question. I make very heavy
use of JavaFX, and I am uncertain what you mean by...
> It would remove the problematic dependency on JavaFX
Could you amplify a bit the "problematic dependency" phrase?
Thank you in advance.
-- Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
