If OpenJDK 11 is the only JDK installed, nothing else needs to be changed. The changes to the eclipse.ini must be made after the installation of e(fx)clipse, otherwise Eclipse will not start again. Furthermore, the path must not be terminated with a slash or backslash. Otherwise, the setting would be tacitly ignored. We don't use quotation marks, even if the path contains spaces. Note: We adjust the path to the OpenJFX libraries according to the operating system and the location in the file system. We finish Eclipse and insert the following lines below the "-vmargs" line into the eclipse.ini file ("-add-modules=ALL-SYSTEM" does not need to be re-inserted if already available): =.osgi We install e(fx)clipse at least in version 3.6.0 in our Eclipse environment (Update-Site: ). We download OpenJFX SDKand store it in a directory. We download and install a new Eclipse IDE, ideally for Eclipse committers. In the following we on the one hand convert our development environment to OpenJDK 11 with OpenJFX and e(fx)clipse, and then turn to the transition for our development, including compiler and launch configurations. e(fx)clipse – IDE – PDE (Version 3.6.0).We use JavaFX in our YAKINDU products and have successfully and successfully converted the development of the GEF framework to the following configuration: However, this article focuses on using e(fx)clipse and the OpenJFX SDK. One would be to use a JDK distribution that delivers Java 11 with JavaFX, such as Bellsoft's Liberica JDK. There are several solutions to this problem.
The first hurdle is already apparent when switching to Java 11, because JavaFX is no longer part of the JDK, either at Oracle or in the open source distribution OpenJDK. JavaFX is no longer a JRE component from Java 11
0 kommentar(er)
