Hi Rory,
I have finished verifying the Derby compile/test cycle against JDK 9
build 116. It took a while because build 116 removes the autoboxing
constructors. This created a huge spew of deprecation warnings for
Derby, much of whose code dates back to Java 1.2-1.4. Eliminating those
warnings was a painstaking task comparable to the removal of
generics-related warnings under Java 5. Even so, I made a couple
blunders (see https://issues.apache.org/jira/browse/DERBY-6856). It may
be possible for IDEs to automate much of this chore. However, my
mistakes suggest that there will still be subtle consequences which an
IDE cannot predict. I expect that many old Java applications will have a
similar experience. Weblogic comes to mind.
Thanks,
-Rick
On 4/29/16 5:57 AM, Rory O'Donnell wrote:
Hi Rick,
Thanks again for the update on Derby & JDK 9.
Early Access b116 <https://jdk9.java.net/download/> for JDK 9 is
available on java.net, summary of changes are listed here
<http://download.java.net/java/jdk9/changes/jdk-9+116.html>.
Early Access b115 <https://jdk9.java.net/jigsaw/> (#4909) for JDK 9
with Project Jigsaw is available on java.net.
Recent changes:
* in b114
o Replace
–com.apple.eawt
–com.apple.eio
With platform independent alternatives in java.awt
* in b115
o As per JEP 260, all non-Critical types/members should be
moved out of
sun/reflect and placed into a non-exported package. Only
critical APIs
should remain in sun.reflect.
We are very interested in hearing your experiences in testing any
Early Access builds. Have you have begun testing against
JDK 9 and or JDK 9 with Project Jigsaw EA builds, have you uncovered
showstopper issues that you would like to discuss?
We would really like to hear your findings so far, either reply to me
or via the mailing lists [1], [2].
Rgds,Rory
[1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/
[2] http://mail.openjdk.java.net/pipermail/jdk9-dev/
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin,Ireland
