Eclipse Community Forums: e(fx)clipse » Eclipse 3.x + compatibility layer + e(fx)clipse 2.3.0

Help

Home

Home » Eclipse Projects » e(fx)clipse » Eclipse 3.x + compatibility layer + e(fx)clipse 2.3.0

Show: Today's Messages :: Show Polls :: Message Navigator

Eclipse 3.x + compatibility layer + e(fx)clipse 2.3.0 [message #1727359]

Tue, 22 March 2016 12:32

Quang Tran

Messages: 25
Registered: June 2012

Junior Member

Hi,
My target platform is 4.5.2, my JDK is 8 update 60
1.) I added the following bundles in my target platform:
org.eclipse.fx.ui.workbench3
org.eclipse.fx.osgi
org.eclipse.fx.javafx

2.) For VM arguments I added -Dosgi.framework.extensions=org.eclipse.fx.osgi
As far as I understood -Dorg.osgi.framework.bundle.parent=ext is only used for e4 + JavaFX applications

3.) I have no imported JavaFX packages in any plugin

5.) Why do I get java.lang.NoClassDefFoundError: javafx/scene/Node?

4.) I don't need to copy the jfxswt.jar to the ext folder because e(fx)clipse should resolve the jar? I even tried to copy the jar to the ext folder but still get NoClassDefFoundError

Report message to a moderator

Re: Eclipse 3.x + compatibility layer + e(fx)clipse 2.3.0 [message #1727364 is a reply to message #1727359]

Tue, 22 March 2016 12:55

Thomas Schindl

Messages: 6651
Registered: July 2009

Senior Member

On 22.03.16 13:32, Quang Tran wrote:
> Hi, My target platform is 4.5.2, my JDK is 8 update 60
> 1.) I added the following bundles in my target platform:
> org.eclipse.fx.ui.workbench3
> org.eclipse.fx.osgi
> org.eclipse.fx.javafx
>

it is important that org.eclipse.osgi and org.eclipse.fx.osgi are
physically next to each other on the filesystem. How are you defining
your target-platform!

org.eclipse.fx.javafx is not needed anymore and only shipped because we
could break existing customers if we'd remove it.

> 2.) For VM arguments I added
> -Dosgi.framework.extensions=org.eclipse.fx.osgi
> As far as I understood -Dorg.osgi.framework.bundle.parent=ext is only
> used for e4 + JavaFX applications

This is correct and for the SWT-Integration always have to have the
OSGi-Hooks active!

>
> 3.) I have no imported JavaFX packages in any plugin
>

That's correct.

> 5.) Why do I get java.lang.NoClassDefFoundError: javafx/scene/Node?
>

What VM are you launching with? Does it have javafx?

> 4.) I don't need to copy the jfxswt.jar to the ext folder because
> e(fx)clipse should resolve the jar? I even tried to copy the jar to the
> ext folder but still get NoClassDefFoundError
>

Right but the exception you show has nothing to do with the SWT-Integration.

You can check if the Hooks are active by setting
-Defxclipse.osgi.hook.debug=true VM arguments field in the launch config.

Tom

Report message to a moderator

Re: Eclipse 3.x + compatibility layer + e(fx)clipse 2.3.0 [message #1727439 is a reply to message #1727359]

Wed, 23 March 2016 07:27

Quang Tran

Messages: 25
Registered: June 2012

Junior Member

Hi Tom,
org.eclipse.osgi was the right hint! It was not physically next to org.eclipse.fx.osgi

Now everything is working as expected.

Thanks for the help.

Quang

Report message to a moderator

Previous Topic:	Multiple Application.launch() from Plugin jobs
Next Topic:	Tutorial4 not generating jemmy projects

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 23:04:32 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter