Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » e(fx)clipse » EFX Tooling and Runtime 2022 release plan ?
EFX Tooling and Runtime 2022 release plan ? [message #1850337] Fri, 25 February 2022 13:40 Go to next message
Stephane  fournier is currently offline Stephane fournierFriend
Messages: 337
Registered: July 2009
Senior Member
Hi,
Do you have any news about the efx release plan for 2022 please ?

I checked this link https://projects.eclipse.org/projects/technology.efxclipse/governance but nothing about 3.8.0 release.

I will be happy to get some news about a potential target update.
Current one is based on 2019-12 eclipse platform.

By the way, I notice when running with AdoptOpenJDK 11, on macOS Intel, with OpenJFX 16 or 17, e4 RCP app's startup is increased by 2.
Splash screen is hidden too soon.

Stepping back to OpenJFX 15.0.2, app's startup is as usal.

Does anyone have seen similar issue ?

Regards,
Stéphane.

Re: EFX Tooling and Runtime 2022 release plan ? [message #1850469 is a reply to message #1850337] Fri, 04 March 2022 00:26 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6648
Registered: July 2009
Senior Member
So 3.8.0 is around the corner and once that is done we'll lift the whole platform to the latest Eclipse Release which will probably be 2022-03.
Re: EFX Tooling and Runtime 2022 release plan ? [message #1850470 is a reply to message #1850469] Fri, 04 March 2022 00:27 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6648
Registered: July 2009
Senior Member
On the performance hit for OpenJFX 16/17 - please file an issue so that we can investigate what is the reason and if we can do anything to mitigate it.
Re: EFX Tooling and Runtime 2022 release plan ? [message #1850490 is a reply to message #1850470] Fri, 04 March 2022 20:28 Go to previous messageGo to next message
Stephane  fournier is currently offline Stephane fournierFriend
Messages: 337
Registered: July 2009
Senior Member
Hi Tom,
I've just filed this ticket : https://bugs.eclipse.org/bugs/show_bug.cgi?id=579095.

Many thanks for the news about future EFX releases.

Regards,
Stéphane

Thomas Schindl wrote on Fri, 04 March 2022 01:27
On the performance hit for OpenJFX 16/17 - please file an issue so that we can investigate what is the reason and if we can do anything to mitigate it.

Re: EFX Tooling and Runtime 2022 release plan ? [message #1851562 is a reply to message #1850469] Fri, 08 April 2022 13:27 Go to previous messageGo to next message
Stephane  fournier is currently offline Stephane fournierFriend
Messages: 337
Registered: July 2009
Senior Member
Hi Tom,
Do you have info regarding the release 3.8.0 please ?

While updating Eclipse IDE to 2022-03 and resintalling EFX Tooling nightly build, I observed CSS Editor is broken due to update in xtend dependencies.

We can install the features but at runtime Eclipse Errors view displays errors for css.ui bundle.
It complains about not finding the proper version of com.google.inject bundle.
Indeed, after installation of EFX tooling, my IDE ended up with 2 bundles com.google.inject 3.0.0 and 5.0.1...

The up-to-date one is loaded and it breaks the EFX CSS editor.

I also notice I was not able anymore to run e4 / EFX app from this env.
It seems JavaFX is not found while starting.

Reverting to 2021-12 and EFX nightly build solved the run issue but surprise ;D it does not resolve the CSS Editor issue.
When installing EFX tooling it now fetchs a (too) recent xtend (and its dependencies) that take this 5.0.1 version of com.google.inject.

Definitely, an update version of the tooling running properly on 2022-03 or 2021-12 would be appreciated for all EFX adopters.

I had to use a backup of my PC to retrieve a functionnal Eclipse IDE with EFX in it.

Regards,
Stéphane


Thomas Schindl wrote on Fri, 04 March 2022 01:26
So 3.8.0 is around the corner and once that is done we'll lift the whole platform to the latest Eclipse Release which will probably be 2022-03.

Re: EFX Tooling and Runtime 2022 release plan ? [message #1851619 is a reply to message #1851562] Mon, 11 April 2022 11:15 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6648
Registered: July 2009
Senior Member
Wow I see - so it is interesting that p2 allows you to install stuff because we use guice and have set the version range to [1.3.0, 2.0.0) and 5.0.1 is installed I would have expected that it refuses to install efxclipse all together.
Re: EFX Tooling and Runtime 2022 release plan ? [message #1851649 is a reply to message #1851619] Mon, 11 April 2022 16:43 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6648
Registered: July 2009
Senior Member
I fixed it - so the latest nightly should work fine on 2022-03
Re: EFX Tooling and Runtime 2022 release plan ? [message #1851726 is a reply to message #1851649] Wed, 13 April 2022 20:59 Go to previous messageGo to next message
Stephane  fournier is currently offline Stephane fournierFriend
Messages: 337
Registered: July 2009
Senior Member
Hi Tom,
Thank you CSS editor is running fine now with this new release.

But I got an error when launching my app from Eclipse as usual (from its product).
Never see such an error before in almost 20 years of RCP app :-(

Do you have an idea ?

I'm still using the same TP : 2019-12 + EFX 3.7.0 runtime as before updating my IDE to 2022-03.

Switching back to IDE 2021-12 + EFX 3.7.0 tooling, everything runs fine again.


After some tests, a basic RCP application tracing "Hello World" in console based on a TP 2019-12 is not runnable from IDE 2022-03.
Changing the TP to IDE itself, this app runs smoothly.

I don't know what the IDE team has done, but they broken something that is supposed to run i.e "use up-to-date IDE against an older Target Platform"

Here the stack I got:
WARNING: Using incubator modules: jdk.incubator.foreign, jdk.incubator.vector
org.osgi.framework.BundleException: Exception in org.eclipse.osgi.internal.framework.SystemBundleActivator.start() of bundle org.eclipse.osgi.
at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:863)
at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:791)
at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1015)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.initWorker(EquinoxBundle.java:197)
at org.eclipse.osgi.container.SystemModule.init(SystemModule.java:99)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle.init(EquinoxBundle.java:280)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle.init(EquinoxBundle.java:264)
at org.eclipse.osgi.launch.Equinox.init(Equinox.java:185)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:316)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:251)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:657)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:594)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
Caused by: org.osgi.framework.BundleException: Failed to create security manager
at org.eclipse.osgi.internal.framework.SystemBundleActivator.installSecurityManager(SystemBundleActivator.java:145)
at org.eclipse.osgi.internal.framework.SystemBundleActivator.start(SystemBundleActivator.java:67)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:842)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:569)
at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:834)
... 17 more
Caused by: java.lang.ClassNotFoundException: allow
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:445)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:587)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:375)
at org.eclipse.osgi.internal.framework.SystemBundleActivator.installSecurityManager(SystemBundleActivator.java:142)
... 22 more

[Updated on: Wed, 13 April 2022 21:39]

Report message to a moderator

Re: EFX Tooling and Runtime 2022 release plan ? [message #1851762 is a reply to message #1851726] Fri, 15 April 2022 07:21 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6648
Registered: July 2009
Senior Member
Well the "allow" is because of the deprecation of the security manager - I need to look deeper and try things myself. I'll come back if I have more information
Re: EFX Tooling and Runtime 2022 release plan ? [message #1851768 is a reply to message #1851762] Fri, 15 April 2022 07:53 Go to previous message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6648
Registered: July 2009
Senior Member
My assumption was/is correct the reason is that to make Equinox work we need to run with "allow" (see https://openjdk.java.net/jeps/411) but as the equinox packaged in our target is too old we'll fail. So the only option I see until we lifted the target is that you add a current Equinox release to your target platform and make sure it is picked upon launching.
Previous Topic:Unable to instantiate class that extends FXViewpart
Next Topic:Eclipse RCP + DriftFX
Goto Forum:
  


Current Time: Mon Oct 03 02:01:58 GMT 2022

Powered by FUDForum. Page generated in 0.02374 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top