[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-openjfx-dev
Subject:    Re: Problem running tests in module controls inside Eclipse
From:       fastegal () swingempire ! de
Date:       2018-11-18 16:48:53
Message-ID: 20181118174853.Horde.2vIeVwoUnIStLSXltaHOXw4 () webmail ! df ! eu
[Download RAW message or body]


arrrggg .. head on desktop edited the arg-file of base project, not  
that of the controls ... now it's time to call it a day, tsssee

thanks for your help! and have a nice evening everybody :)

Zitat von Tom Schindl <tom.schindl@bestsolution.at>:

> i run them with
> 
> -Djava.library.path=/Users/tomschindl/OpenJFX/openjdk-jfx/build/sdk/lib
> -Djavafx.toolkit=test.com.sun.javafx.pgstub.StubToolkit
> 
> Tom
> 
> On 18.11.18 17:00, Nir Lisker wrote:
> > I don't recall seeing this problem. Just to be sure, did you circumvent the
> > compilation error in Dialog's lambda?
> > 
> > On Sun, Nov 18, 2018 at 5:42 PM <fastegal@swingempire.de> wrote:
> > 
> > > 
> > > With the step-by-step debugging help provided by nlisker over at
> > > javafxports (https://github.com/javafxports/openjdk-jfx/issues/187 -
> > > which cleaned up some inherent misconception on my part, thanks!) I
> > > managed to run tests in base and graphics from inside Eclipse (right
> > > click and run as/unit test), but not in controls (complete stacktrace
> > > is at the end), barking with essentially:
> > > 
> > > Caused by: java.lang.IllegalStateException: Toolkit not initialized
> > > 
> > > Which is the usual complaint if the fx app thread is not yet started.
> > > For my own tests I have a class rule that fires it up, but how to
> > > start it for openjfx controls tests?
> > > 
> > > The complete stacktrace:
> > > 
> > > java.lang.ExceptionInInitializerError
> > > at
> > > 
> > > javafx.controls/test.javafx.scene.control.TextAreaTest.setup(TextAreaTest.java:53)
> > >  at
> > > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> > > Method)
> > > at
> > > 
> > > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > >  at
> > > 
> > > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > >  at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> > > at
> > > 
> > > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> > >  at
> > > 
> > > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> > >  at
> > > 
> > > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> > >  at
> > > 
> > > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> > > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> > > at
> > > 
> > > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> > >  at
> > > 
> > > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> > >  at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> > > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> > > at
> > > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> > > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> > > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> > > at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> > > at
> > > 
> > > org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> > >  at
> > > 
> > > org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> > > at
> > > 
> > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> > >  at
> > > 
> > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> > >  at
> > > 
> > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> > >  at
> > > 
> > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
> > >  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)
> > > 
> > > 
> > > 
> 
> --
> Tom Schindl, CTO
> BestSolution.at EDV Systemhaus GmbH
> Eduard-Bodem-Gasse 5-7. A-6020 Innsbruck
> Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck


[prev in list] [next in list] [prev in thread] [next in thread]