You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Rick Hillegas <ri...@gmail.com> on 2017/05/20 13:06:20 UTC

Re: JDK 9 EA Build 170 is available on jdk.java.net

Thanks, Rory. With build 170 of jdk 9, Derby compiles cleanly, its 
javadoc compiles cleanly, and its regression tests run cleanly.

Thanks,
-Rick

On 5/19/17 3:10 AM, Rory O'Donnell wrote:
>
>
> Hi Rick,
>
> *
> JDK 9 Early Access*  build 170  is available at the new location : - 
> jdk.java.net/9/
>
> A summary of all the changes in this build are listed here 
> <http://download.java.net/java/jdk9/changes/jdk-9+170.html>.
>
> Changes which were introduced since the last availability email that 
> may be of interest :
>
>   * b168 - JDK-8175814: Update default HttpClient protocol version and
>     optional request version
>       o related to JEP 110  : HTTP/2 Client.
>   * b169 - JDK-8178380 : Module system implementation refresh (5/2017)
>       o changes in command line options
>   * b170 - JDK-8177153  : LambdaMetafactory has default
>     constructorIncompatible change,
>       o release note:  JDK-8180035
>
> *New Proposal - Mark Reinhold has asked for comments on the jigsaw-dev 
> mailing list *[1]
>
>   * Proposal: Allow illegal reflective access by default in JDK 9
>
>     In short, the existing "big kill switch" of the `--permit-illegal-access`
>     option [1] will become the default behavior of the JDK 9 run-time system,
>     though without as many warnings.  The current behavior of JDK 9, in which
>     illegal reflective-access operations from code on the class path are not
>     permitted, will become the default in a future release.  Nothing will
>     change at compile time.
>
>
> Rgds,Rory
>
> [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017-May/012673.html
>
> -- 
> Rgds,Rory O'Donnell
> Quality Engineering Manager
> Oracle EMEA , Dublin, Ireland