You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by Rory O'Donnell <ro...@oracle.com> on 2016/09/20 10:51:38 UTC
Early Access build 136 for JDK 9 & JDK 9 with Project Jigsaw are
available on java.net
Hi Paul,
Early Access b136 <https://jdk9.java.net/download/> for JDK 9 is
available on java.net, summary of changes are listed here
<http://www.java.net/download/java/jdk9/changes/jdk-9+136.html>.
Early Access b136 <https://jdk9.java.net/jigsaw/> (#5506) for JDK 9 with
Project Jigsaw is available on java.net, summary of changes are listed
here
<http://www.java.net/download/java/jigsaw/archive/136/binaries/jdk-9+136.html>.
There have been a number of fixes to bugs reported by Open Source
projects since the last availability email :
* 8165723 - b136 - core-libs JarFile::isMultiRelease() method returns
false when it should return true
* 8165116 - b136 - xml redirect function is not allowed even with
enableExtensionFunctions
NOTE:- Build 135 included a fix for JDK-8161016 which *has introduced a
behavioral change to HttpURLConnection, more info:*
The behavior of HttpURLConnection when using a ProxySelector has been
modified with this JDK release. Currently, HttpURLConnection.connect()
call would fallback to a DIRECT connection attempt if the configured
proxy/proxies failed to make a connection. This release introduces a
change whereby no DIRECT connection will be attempted in such a
scenario. Instead, the HttpURLConnection.connect() method will fail and
throw an IOException which occurred from the last proxy tested. This
behavior now matches with the HTTP connections made by popular web
browsers. But this change will bring compatibility issues for the
applications expecting a DIRECT connection when a proxy server is down
or when wrong proxies are provided.
*
JDK 9 Outreach Survey*
In order to encourage and receive additional feedback from developers
testing their applications with JDK 9,
the OpenJDK Quality Outreach effort has put together a very brief survey
about your experiences with JDK 9 so far.
It is available at***https://www.surveymonkey.de/r/JDK9EA*
We would love to hear feedback from you!
Rgds,Rory
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
Re: Early Access build 136 for JDK 9 & JDK 9 with Project Jigsaw are
available on java.net
Posted by Niclas Hedhman <ni...@hedhman.org>.
For our dev@zest.apache.org subscribers,
We (Paul and I) was approached by Oracle to participate in the community
outreach program, which is seeking the wider Java community to assist
Oracle in getting Java 9 in better shape before the GA Release.
Part of that is that we have a Jenkins build available for Java 9 builds
(thanks Paul), and that they will notify our small community whenever a new
Java 9 build is available.
So, if you don't care much of Java 9, you can ignore these emails.
Niclas
On Tue, Sep 20, 2016 at 6:51 PM, Rory O'Donnell <ro...@oracle.com>
wrote:
>
> Hi Paul,
>
> Early Access b136 <https://jdk9.java.net/download/> for JDK 9 is
> available on java.net, summary of changes are listed here <
> http://www.java.net/download/java/jdk9/changes/jdk-9+136.html>.
> Early Access b136 <https://jdk9.java.net/jigsaw/> (#5506) for JDK 9 with
> Project Jigsaw is available on java.net, summary of changes are listed
> here <http://www.java.net/download/java/jigsaw/archive/136/binari
> es/jdk-9+136.html>.
>
> There have been a number of fixes to bugs reported by Open Source projects
> since the last availability email :
>
> * 8165723 - b136 - core-libs JarFile::isMultiRelease() method returns
> false when it should return true
> * 8165116 - b136 - xml redirect function is not allowed even with
> enableExtensionFunctions
>
> NOTE:- Build 135 included a fix for JDK-8161016 which *has introduced a
> behavioral change to HttpURLConnection, more info:*
>
> The behavior of HttpURLConnection when using a ProxySelector has been
> modified with this JDK release. Currently, HttpURLConnection.connect() call
> would fallback to a DIRECT connection attempt if the configured
> proxy/proxies failed to make a connection. This release introduces a change
> whereby no DIRECT connection will be attempted in such a scenario. Instead,
> the HttpURLConnection.connect() method will fail and throw an IOException
> which occurred from the last proxy tested. This behavior now matches with
> the HTTP connections made by popular web browsers. But this change will
> bring compatibility issues for the applications expecting a DIRECT
> connection when a proxy server is down or when wrong proxies are provided.
> *
>
> JDK 9 Outreach Survey*
>
> In order to encourage and receive additional feedback from developers
> testing their applications with JDK 9,
> the OpenJDK Quality Outreach effort has put together a very brief survey
> about your experiences with JDK 9 so far.
>
> It is available at***https://www.surveymonkey.de/r/JDK9EA*
>
>
> We would love to hear feedback from you!
>
>
> Rgds,Rory
>
> --
> Rgds,Rory O'Donnell
> Quality Engineering Manager
> Oracle EMEA , Dublin, Ireland
>
>
--
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java