Up coming changes for efxclipse 3.9 [message #1851650] |
Mon, 11 April 2022 12:58  |
Eclipse User |
|
|
|
Hi,
Supported Java Versions
We are about to release e(fx)clipse 3.8.0 which will be the last 3.x release providing support for Java-8, we'll lift the platform afterwards and the minimum Java Version from there on will be Java-11. Customers with support contracts can request 3.8.x releases to get bug fixes.
If you have any concerns please follow up at https://github.com/eclipse-efx/efxclipse-rt/issues/449
Licensing change
Currently larg parts of the e(fx)clipse code base are licensed under EPLv1.0, we'll upgrade to EPLv2.0.
If you have concerns please follow up at https://github.com/eclipse-efx/efxclipse-rt/issues/416
My plan is to get 3.9 out of the door very fast (only bugfixes) so that you can all enjoy the upgraded platform but that heavily depends on my day job duties and how much regressions I have to work around from the platform upgrade.
|
|
|
|
|
|
|
|
Re: Up coming changes for efxclipse 3.9 [message #1853467 is a reply to message #1853325] |
Sun, 03 July 2022 12:56   |
Eclipse User |
|
|
|
Hi,
I made this afternoon a try to EFX 3.9.0 snapshot (built on 3.9.0.202206270944) + platform as Eclipse Modeling 2022-06 build.
Since I have my own features to reference EFX + Eclipse platform, I had some time, to fetch additional bundles related to p2 support + jakarta.xml.bind bundle.
At the end, I got a successful app running with the same OpenJDK (Temurin 17.0.3) + OpenJFX version (15.0.1) already used with efx 3.8.0/2019-12 platform.
N.B: Make sure to run your efx app with a freshly created runtime workspace ( same thing for the osgi bundle configuration).
The only thing I had to change is maybe linked to DS removal ?
Indeed, I used extension-point "org.eclipse.e4.workbench.model" to contribute a 'Theme' menu (as in the very old efx contacts app example).
It seems this extension-point is not called anymore by EFX 3.9.0 (in extension-point documentation it is written it is not an API).
is it true ? DefaultThemeManager is still instantiated (no issue).
I've replaced this MenuThemeProcessor, by declaring the menu items in the application.e4xmi file directly and it works.
MenuThemeProcessor class is useless, but all other artefacts remain (class that extends AbstractTheme, ServiceComponent registration in Manifest.MF, Command to switch themes).
As far as I know, 3.9.0-snapshot seems to run as 3.8.0.
Does anyone can provide other feedbacks please ?
Regards,
Stéphane
[Updated on: Sun, 03 July 2022 13:13] by Moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05904 seconds