Hi Rory,

We already test WildFly and all "our" projects WildFly depends on, on both JDK9 builds.
We did find handful of issues with Jigsaw builds which mostly relate back to either issues in jigsaw itself
or problems in JDK itself once it runs on jigsaw.  Which is the biggest thing giving us problems at the moment.
see for details: http://mail.openjdk.java.net/pipermail/jpms-spec-observers/2016-March/000305.html

you can track our progress at our CI at (currently tested from my branches)

and related projects

we also track known issues we found with WildFly at

BTW, what is the reason that jigsaw JDK builds are 5 times size of the non jigsaw builds?
685.27 MB vs 122.12 MB for 32bit linux jdk for example.


On Sat, Mar 19, 2016 at 8:41 AM, Rory O'Donnell <rory.odonnell@oracle.com> wrote:

Hi Jason/Tomaz,

Early Access b110 for JDK 9 is available on java.net, summary of  changes are listed here .
Among other fixes , the following changes are also included from builds 108 to 110
    • removal of the OS X-specific com.apple.concurrent package
    • update to the JAX-WS RI integration to latest version (2.3.0-SNAPSHOT)
    • disabling of Diffie-Hellman keys smaller than 1024 bits
Early Access b110 (#4664) for JDK 9 with Project Jigsaw is available on java.net.
We expect this will be the last EA build before we integrate into JDK 9. This means that this
EA build is essentially what will be jdk-9+111 next week.

As always, please help out by trying out existing code and libraries to see what works and
doesn't work. We have a detailed list of compatibility issues listed in JEP 261 [2].

Also feedback and questions from those that trying the EA build to modularize existing
code would be appreciated. We also want to know what works and doesn't work here [3]


[1] https://jdk9.java.net/jigsaw/
[2] http://openjdk.java.net/jeps/261
[3] http://mail.openjdk.java.net/pipermail/jigsaw-dev/
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin,Ireland