> > The blank final field dialog may not have been initialized Dialog.java
This is mentioned in the note under "Configure Eclipse to use the latest JDK". Did you end up reverting the .classpath and .project files? On Tue, Jan 14, 2020 at 10:37 AM Robert Lichtenberger < r.lichtenber...@gmail.com> wrote: > I've just simply removed the two missing source folders and only one error > remains: > * The blank final field dialog may not have been initialized Dialog.java > /controls/src/main/java/javafx/scene/control line 521 > which seems to me like an error within the eclipse compiler. > > Ignoring this error, I've tried to execute > test.javafx.scene.control.ButtonTest from the IDE but get: > > > Graphics Device initialization failed for : es2, sw > > Error initializing QuantumRenderer: no suitable pipeline found > > java.lang.RuntimeException: java.lang.RuntimeException: Error > initializing > > QuantumRenderer: no suitable pipeline found > > at > > > javafx.graphics/com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:280) > > ... > > > Debugging into com.sun.prism.GraphicsPipeline I can see that for > com.sun.prism.es2.ES2Pipeline I get this exception: > java.lang.UnsatisfiedLinkError: no prism_es2 in java.library.path: > [/usr/lib64/mysql, /opt/synedra/lib/opencv-dcm, > /home/rli/devel/repository/tool/linux/64, ., /usr/java/packages/lib, > /usr/lib64, /lib64, /lib, /usr/lib] > > As mentioned on the wiki, I've added > > -Djava.library.path=/home/rli/PWEs/jfx/modules/javafx.graphics/build/module-lib > as VM argument which fixes the loading of ES2Pipeline. > > However I still can't run the test, I get: > java.lang.ExceptionInInitializerError > at > > javafx.controls/test.javafx.scene.control.ButtonTest.setup(ButtonTest.java:83) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > ... > Caused by: java.lang.IllegalStateException: Toolkit not initialized > at > > javafx.graphics/com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:410) > at > > javafx.graphics/com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:405) > at > > javafx.graphics/com.sun.javafx.application.PlatformImpl.setPlatformUserAgentStylesheet(PlatformImpl.java:695) > at > > javafx.graphics/com.sun.javafx.application.PlatformImpl.setDefaultPlatformUserAgentStylesheet(PlatformImpl.java:657) > at javafx.controls/javafx.scene.control.Control.<clinit>(Control.java:99) > ... 25 more > > java.lang.NullPointerException > at > > javafx.controls/test.javafx.scene.control.ButtonTest.after(ButtonTest.java:93) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > ... > > it seems the test does not wait for the toolkit to be initialized ... > > Am Di., 14. Jan. 2020 um 09:11 Uhr schrieb Robert Lichtenberger < > r.lichtenber...@gmail.com>: > > > I've tried to import using "General" -> "Existing Projects in Workspace" > > but get lots of errors as well. When reducing the imported projects to > > base, graphics and controls: > > * base is ok > > * graphics has these errors: > > Description Resource Path Location Type > > Project 'graphics' is missing required source folder: 'build/hlsl/Decora' > > graphics Build path Build Path Problem > > Project 'graphics' is missing required source folder: 'build/hlsl/Prism' > > graphics Build path Build Path Problem > > * controls won't build due to errors in graphics > > > > Is hlsl the "High Level Shading Language" which may be specific to > Windows? > > > > Am Di., 14. Jan. 2020 um 08:53 Uhr schrieb Tom Schindl < > > tom.schi...@bestsolution.at>: > > > >> Hi, > >> > >> I think Nir nor I uses them as gradle Projects because you have the > >> .classpath, .project, ... . > >> > >> Tom > >> > >> On 14.01.20 08:12, Robert Lichtenberger wrote: > >> > Yes, I did run a gradle build (for which I had to tweak > >> > buildSrc/linux.gradle to ignore some deprecations -- see my other post > >> to > >> > the list) successfully. > >> > > >> > I use a completely fresh workspace, updated my JFX sources, I use > >> Eclipse > >> > 2019-12 and jdk-13.0.1+9 on Fedora 31. > >> > > >> > These are my steps: > >> > * open eclipse, > >> > * choose "Import projects" then "Gradle" -> "Existing Gradle project" > >> > * give the top level folder of my repository (/home/rli/PWEs/jfx in my > >> case) > >> > * Use the gradle wrapper (i.e. no changes on the wizards next page) > >> > * The project structure is given correctly, so I click finish > >> > > >> > Eclipse then loads the projects but gives out the aforementioned > error. > >> > > >> > I've made a 1-minute video clip showing my steps: > >> > https://youtu.be/S9WnOHCbWLI > >> > > >> > I'll try to find out what is going wrong here. Could you tell me which > >> > versions (JFX sources, Eclipse, JDK) you are using? > >> > > >> > > >> > Am Mo., 13. Jan. 2020 um 17:59 Uhr schrieb Nir Lisker < > >> nlis...@gmail.com>: > >> > > >> >> Never seen this problem before. Did you run a Gradle build? [1] It > >> needs to > >> >> generated required resources. > >> >> > >> >> Also, the Eclipse files for some projects are not updated (though for > >> the > >> >> modules they are fine, so it's not the problem you are having). My > >> patch > >> >> for them was pending review by other Eclipse users and no one tested > >> it, so > >> >> if you are up for it I could resume work on it. > >> >> > >> >> - Nir > >> >> > >> >> [1] > >> >> > >> >> > >> > https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-BuildandTest > >> >> > >> >> On Mon, Jan 13, 2020 at 5:35 PM Robert Lichtenberger < > >> >> r.lichtenber...@synedra.com> wrote: > >> >> > >> >>> Hmm. Eclipse would suit me fine, so I've tried to import a current > >> >> OpenJFX > >> >>> repository to Eclipse but it gives me (among others) this error: > >> >>> > >> >>> Description Resource Path Location Type > >> >>> Cannot nest > >> >>> > >> >> > >> > 'home/rli/PWEs/jfx/modules/javafx.base/build/classes/java/main/javafx.base' > >> >>> inside library > >> >>> 'home/rli/PWEs/jfx/modules/javafx.base/build/classes/java/main' > >> base > >> >>> Build path Build Path Problem > >> >>> > >> >>> The Workspace was completely new, all the other stuff (JDK 12, Java > >> >>> Compiliance Level) should be ok. > >> >>> > >> >>> Do you have any idea what is going wrong here? Smells like module > >> system > >> >>> problems :-(. > >> >>> > >> >>> > >> >>> Best regards, > >> >>> > >> >>> Robert > >> >>> On 2020-01-10 17:52, Nir Lisker wrote: > >> >>> > >> >>> Hi Robert, > >> >>> > >> >>> I've brought this up in the past. > >> >>> > >> >>> I think that the best solution is for someone from the community to > >> take > >> >>> that task. I try to keep the Eclipse section updated, we will need > >> >> someone > >> >>> for the other IDE's. > >> >>> > >> >>> - Nir > >> >>> > >> >>> On Fri, Jan 10, 2020 at 10:54 AM Robert Lichtenberger < > >> >>> r.lichtenber...@gmail.com> wrote: > >> >>> > >> >>>> I've noticed that > >> >>>> https://wiki.openjdk.java.net/display/OpenJFX/Using+an+IDE > >> >>>> seems a bit outdated (refers to JDK 1.8, a folder named "rt", which > >> no > >> >>>> longer exists, etc.). > >> >>>> > >> >>>> Could someone please update this page so that it is easier for > >> newcomers > >> >>>> to > >> >>>> dive into the development of OpenJFX. > >> >>>> > >> >>>> Thanks, > >> >>>> Robert > >> >>>> > >> >>> > >> >> > >> > >> -- > >> Tom Schindl, CTO > >> BestSolution.at EDV Systemhaus GmbH > >> Salurnerstrasse 15. A-6020 Innsbruck > >> Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck > >> > > >
