e(fx)clipse + SWT + JavaFX JDK8b113


Starting with build 113 of Java8 the FX-Team made the wise decision to move the SWT integration into its own jar which is not on any default classpath.

This is a very wise decision because the javafxrt.jar is on the extension classpath and has been holding classes who depend on swt which is a client library typically found on the application classpath or in OSGi in the Classloader of the SWT-OSGi-Bundle.

I guess you can imagine how hard is was for e(fx)clipse to give OSGi-User the FXCanvas integration. This problem is gone now. The latest nightly build can deal with the changes on the JDK-Level (for FX2 the classloading magic is still in).

In case you are developing with JavaFX and need the SWT-Integration you’ll have to update to the latest bits in case you use JDK8b113 and above.

About these ads

No comments yet... Be the first to leave a reply!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 665 other followers

%d bloggers like this: