HEADS-UP: jfxrt.jar moving to jre/lib/ext

Kevin Rushforth kevin.rushforth at oracle.com
Thu Jan 24 09:32:13 PST 2013

Richard Bair wrote:
>> 3) Tools, scripts, programs that "know" where jfxrt.jar is relative to the root of the JRE will have to be adjusted accordingly, to either look for it in lib/ext or, if appropriate, just rely on the fact that it is now on the classpath. For example, when opening a JavaFX project in NB 7.2, it may not recognize your JDK8 as being JavaFX-capable. A future version of NB will add support for JDK 8 / FX 8.
> We should make sure this is posted widely and easily discoverable via Google searches on "why doesn't Java 8 work with FX" or something along those lines.

Good point. I will also reach out to the NB team to get an update on 
when the version of NB with JDK 8 support will be ready (and when they 
might be able to include support for the new location).

>> 4) Because we still include the javafx.embed.swt package in jfxrt.jar -- see http://javafx-jira.kenai.com/browse/RT-23041 -- applications that access javafx.embed.swt.FXCanvas will need to put the swt.jar library on the boot classpath in order for it to run.
> Putting swt.jar on the normal class path won't cut it?

No, that is what will stop working as a result of this.

-- Kevin

More information about the openjfx-dev mailing list