Hi Rory,
I have compiled and tested Derby against JDK 9 build 181. I have tested
3 versions of Derby:
1) The current 10.13.1.1 release running on the JDK9b181 platform.
2) The Derby development trunk, compiled with JDK 8 and running on the
JDK9b181 platform. The development trunk is very close to the next
release of Derby, which we expect to publish later this year.
3) A modified version of Derby, compiled with JDK9b181 and running on
that platform.
The test results were clean. See
https://issues.apache.org/jira/browse/DERBY-6856?focusedCommentId=16124749&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16124749
I have invited the user community to test their Derby-powered apps
against JDK9b181:
http://apache-database.10148.n7.nabble.com/derby-is-ready-for-JDK-9-td147846.html
I will let you know if our users report any problems.
In my opinion, Derby is ready for JDK 9. You are welcome to add any of
this evidence to the JDK 9 readiness page.
Thanks,
-Rick
On 8/8/17 2:37 AM, Rory O'Donnell wrote:
Hi Rick,
Thank you very much for all your testing of JDK 9 during its
development! Such contributions have significantly helped shape and
improve JDK 9.
Now that we have reached the JDK 9 Final Release Candidate phase [1] ,
I would like to ask if your project can be considered to be 'ready for
JDK 9', or if there are any remaining show stopper issues which you've
encountered when testing with the JDK 9 release candidate.
JDK 9 b181 is available at http://jdk.java.net/9/
If you have a public web page, mailing list post, or even a tweet
announcing you project's readiness for JDK 9, I'd love to add the URL
to the upcoming JDK 9 readiness page on the Quality Outreach wiki.
Looking forward to hearing from you,
Rory
[1] http://openjdk.java.net/projects/jdk9/
