Testing your JavaFX applications on JDK 9
kevin.rushforth at oracle.com
Tue Jan 17 13:41:49 UTC 2017
Exactly. I would add that any tests that need Robot or
PerformanceTracker will need to use "--add-exports" to add the necessary
qualified exports on the command line as there is no public API for those.
Jonathan Giles wrote:
> Platform.firePulse() never existed, you're probably thinking of
> Toolkit.firePulse() (which is not public API)?
> A close replacement is Platform.requestNextPulse().
> -- Jonathan
> On 17/01/17 10:00 AM, Tom Eugelink wrote:
>> One of the methods I use a lot in Tests, to make sure something has
>> happened, is:
>> runAndWait( () -> Platform.firePulse() );
>> firePulse no longer exists. Is there a replacement?
>> The rest seems to compile ok. But I cannot run the tests ATM.
>> On 11-1-2017 20:14, Kevin Rushforth wrote:
>>> As you may know JDK 9 has hit the feature extension complete
>>> milestone . We still have a small number of weeks to fix P1-P3
>>> bugs, but we need to know about them in order to fix them. Our focus
>>> will be on bugs that are new in JDK 9 (regressions).
>>> I ask all JavaFX developers to please download JDK 9 early access
>>>  and test your application. You can report any bugs via
>>> bugs.java.com . If you have any questions about whether a
>>> behavior is a bug or is expected, please ask on this alias or on the
>>> jigsaw-dev alias .
>>> Thank you.
>>> -- Kevin
>>>  http://openjdk.java.net/projects/jdk9/
>>>  https://jdk9.java.net/download/
>>>  http://bugreport.java.com/
>>>  jigsaw-dev at openjdk.java.net
More information about the openjfx-dev