Why isn't JavaFX on the jdk1.7.0_u10build12 class path?
zonski at gmail.com
Tue Oct 23 19:55:44 PDT 2012
Given that the bootclasspath issue will (one day) be fixed so that JFX is
actually co-bundled, I'd personally just go with manually 'fixing' your
installed JDK by moving JFX inside the JDK extension package after the
Then when the classpath issue finally gets resolved, no changes will be
needed to your Maven POM etc.
If you use the assembly tools (or
https://github.com/zonski/javafx-maven-plugin) then JFX gets bundled into
the disputables so no need to do any hackery on that side of things (i.e.
you only have to do the above cludge on your own dev machine where you do
On Wed, Oct 24, 2012 at 1:00 PM, Scott Palmer <swpalmer at gmail.com> wrote:
> JavaFX has been bundled since 7u7 anyway… but it is not on the classpath
> by default. Presumably someone was scared of breaking stuff. The JavaFX
> app packager does some magic to get it on the classpath for runtime.
> For Maven there are a couple of options. One is to use the dreaded
> "system" scope:
> Use the "enforcer" plugin to require at lest 7u7.
> And then do the same sort of classpath hackery that the app packager stubs
> do for runtime. Or just use -Xbootclasspath/a:
> On 2012-10-23, at 9:37 PM, Randahl Fink Isaksen <randahl at rockit.dk> wrote:
> > I upgraded to jdk 7u10 build 12 and I can see it comes with a JavaFX
> 2.2.4 inside it. So I thought I would go ahead and remove my maven
> dependency on the trusty old JavaFX 2.2.0-b19.
> > However when I try to build my application with NetBeans it does not
> find the JavaFX classes. If I open the Java platform manager in NetBeans it
> also shows that jfxrt.jar is not on the class path of the JDK 1.7 (default)
> > Am I supposed to still extract the jfxrt.jar and the dylibs and manually
> create a maven dependency, or have I overlooked something here?
> > Thanks
> > Randahl
More information about the openjfx-dev