JDK 14 - Early Access build 19 is available
Deepak Damodaran
deepak.n.damodaran at oracle.com
Sat Oct 19 17:36:41 UTC 2019
*JDK 14 - Early Access build 19 is available via artifactory [1]*
These early-access, open-source builds are provided under the GNU
General Public License, version 2, with the Classpath Exception
<http://openjdk.java.net/legal/gplv2+ce.html>.
* Release notes
o https://jdk.java.net/14/release-notes
* JEPs targeted to JDK 14, so far
o 352 - Non-Volatile Mapped Byte Buffers
<https://openjdk.java.net/jeps/352>
o 358 - Helpful NullPointerExceptions
<http://openjdk.java.net/jeps/358>
o 349 - JFR Event Streaming <https://openjdk.java.net/jeps/349>
* Changes in this build
<http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-14%2B16%22%3A%3A%22jdk-14%2B17%22-%22jdk-14%2B16%22%29&revcount=1000>
* Recent Bug fixes of Interest
o Build 18:-
+ JDK-8231260: (dc) DatagramChannel::disconnect changes the
port of the local address to 0 (lnx)
+ JDK-8223771: FileSystemProvider.newFileSystem(Path, Map)
should throw IOException when called with a file that cannot
be open
I want to draw your attention to some *noteable changes in previous
builds of JDK 14.*
o Build 14 - Classes are now loaded and linked by Class.forName()
(JDK-8212117 <https://bugs.openjdk.java.net/browse/JDK-8212117>)
+ we need help testing changes to 3-arg Class.forName method.
The method has always been specified to link the class but
the implementation has historically not done this when
invoked with the "initialize" parameter set to false. The
bug has been fixed in JDK 14 but it has the potential to
change the behavior of code that uses Class.forName to load
classes that cannot be linked.
Regards
Deepak Damodaran
[1] https://jpg-data.us.oracle.com/artifactory/re-release-local/jdk/14/
More information about the adoption-discuss
mailing list