Default e4 application project has errors [message #1819525] |
Thu, 16 January 2020 18:33  |
Eclipse User |
|
|
|
Hello,
Apart from the other problem I am having with my e4 application and java11, I am having a problem simply getting the default e4 application to run.
Even using a fresh (and latest, i.e. "eclipse-jee-2019-12-R-win32-x86_64" eclipse version, the default e4 application project shows errors and doesn't launch.
I changed the preferences, such that "JavaFX" -> "JavaFX 11 + SDK" points to the lib folder of the javafx-sdk (I tried the root folder as well, doesn't change anything), installed e(fx)clipse 3.6.0 via the market place and created a new "JavaFX" -> "OSGI" -> "e4 Application projects".
Then I get the following errors:
AbstractTheme cannot be resolved to a type DefaultTheme.java /test.app/src/test/app/themes line 5 Java Problem
The import org.eclipse.fx cannot be resolved DefaultTheme.java /test.app/src/test/app/themes line 3 Java Problem
Bundle 'org.eclipse.fx.core.databinding' cannot be resolved MANIFEST.MF /test.app/META-INF line 17 Plug-in Problem
Bundle 'org.eclipse.fx.ui.databinding' cannot be resolved MANIFEST.MF /test.app/META-INF line 18 Plug-in Problem
Bundle 'org.eclipse.fx.ui.di' cannot be resolved MANIFEST.MF /test.app/META-INF line 15 Plug-in Problem
Bundle 'org.eclipse.fx.ui.services' cannot be resolved MANIFEST.MF /test.app/META-INF line 24 Plug-in Problem
Bundle 'org.eclipse.fx.ui.theme' cannot be resolved MANIFEST.MF /test.app/META-INF line 14 Plug-in Problem
Bundle 'org.eclipse.fx.ui.workbench.fx' cannot be resolved MANIFEST.MF /test.app/META-INF line 8 Plug-in Problem
'Automatic-Module-Name' header is required to be discoverable as a Java module in a Java modular setup (Java 9 and later) MANIFEST.MF /test.app/META-INF line 1 Plug-in Problem
An entry for test.app/Application.e4xmi is required in bin.includes build.properties /test.app line 1 Plug-in Problem
I tried with both AdoptOpenJDK11 and AdoptOpenJDK13.
This doesn't seem healthy...
|
|
|
|
|
|
|
|
|
Re: Default e4 application project has errors [message #1820898 is a reply to message #1820774] |
Fri, 31 January 2020 09:37   |
Eclipse User |
|
|
|
Wow, perfect. That is exactly what I was looking for!
I'm following your blog post to the letter, but the step where the local javafx jars from the javafx sdk's lib folder should show up as/under "Plug-in Dependencies" just does not happen (the lib folder is set in the eclipse JavaFX SDK path setting and the target platform for Plug-in Development is also set exactly as in your blog post):

I think that is the final step that is missing in order to get this running.
Do you have any idea what is preventing it from detecting the javafx jars as plugin dependencies?
Also: Thanks a lot for the part on running the application as well! That will be super helpful, once it compiles.
Thanks a lot and sorry for replying so late. Somehow this forum seems to always automagically unsubscribe me from my subscribed topics, instead of notifying me (never got a notification so far) -.-
|
|
|
Re: Default e4 application project has errors [message #1820900 is a reply to message #1820898] |
Fri, 31 January 2020 09:46   |
Eclipse User |
|
|
|
Oh boy. I got it!
I've used the AdoptOpenJDK13 instead of 11. Changing it and then restarting eclipse and reloading the target platform did the trick! Sorry and thanks! :)
I don't really understand why this happens with JDK13, but for now I'm just happy it works. :)
|
|
|
Re: Default e4 application project has errors [message #1820903 is a reply to message #1820900] |
Fri, 31 January 2020 10:26   |
Eclipse User |
|
|
|
Yeah! It works!
I was especially interested in the second option ("running with bundles javafx-modules") and got it running.
I feel like you should mention/stress that the "-Dosgi.framework.extensions=org.eclipse.fx.osgi" VM argument seems to be the one that is really necessary! It does not seem to be added by default and (if I am not mistaken) was only visible in one of your screenshots, but that one seems to be what does the trick!
Also, if you add the VM arg in the product file under the "Launching" tab and either add the javafx features and the org.eclipse.fx.runtime.e4fx.feature as included features in the feature.xml or as Features in the Content tab of the product file, you don't have to manipulate the run configuration (by hand) at all. You can just generate it by launching through the product file once.
Thanks a lot. That blog post was/is pure gold!
|
|
|
|
Powered by
FUDForum. Page generated in 0.03920 seconds