Early Access builds of JDK 9 b118 & JDK 9 with Project Jigsaw, b118 (#4987) are available on java.net
"Rory O'Donnell" <[email protected]> Wed, 18 May 2016 09:45:30 +0100
| Newsgroups | gmane.comp.java.cruise-control.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============1944648998116788894==
Content-Type: multipart/alternative;
boundary="------------1766302E4CA621807F143591"
This is a multi-part message in MIME format.
--------------1766302E4CA621807F143591
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi Kent,
Early Access b118 <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+118.html>.
Early Access b118 <https://jdk9.java.net/jigsaw/> (#4913) for JDK 9 with
Project Jigsaw is available on java.net.
JDK 9 Build 118 includes a refresh of the module system.
There are several changes in this update, JDK 9 b118 has the updated
policy for root modules described
in JEP 261 [1]. This means that java.corba and the 6 EE modules aren't
resolved by default and so it will
look "as if" the types in these modules have been removed. More info on
the JDK 9 dev mailing list [2].
A change that went into JDK 9 b102 is worth mentioning:
JDK9: Remove stopThread RuntimePermission from the default java.policy
In previous releases, untrusted
code had the "stopThread" RuntimePermission granted by default. This
permission allows untrusted code
to call Thread.stop(), initiating an asynchronous ThreadDeath Error, on
threads in the same thread group.
Having a ThreadDeath Error thrown asynchronously is not something that
trusted code should be expected
to handle gracefully. The permission is no longer granted by default.
Rgds,Rory
[1] http://openjdk.java.net/jeps/261
[2] http://mail.openjdk.java.net/pipermail/jdk9-dev/2016-May/004309.html
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin,Ireland
--------------1766302E4CA621807F143591
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by aserp1040.oracle.com id
u4I8jhTV023873
<html>
<head>
<meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf=
-8">
</head>
<body bgcolor=3D"#FFFFFF" text=3D"#000000">
<br>
<p>Hi Kent, </p>
<p>Early Access <a href=3D"https://jdk9.java.net/download/">b118</a>
for JDK 9 is available on java.net, summary of=C2=A0 changes are li=
sted
<a
href=3D"http://www.java.net/download/java/jdk9/changes/jdk-9+118.=
html">here
</a>.</p>
<p>Early Access <a href=3D"https://jdk9.java.net/jigsaw/">b118</a> <f=
ont
size=3D"4">(#4913) </font>for JDK 9 with Project Jigsaw=C2=A0is
available on java.net. </p>
<p>JDK 9 Build 118 includes a refresh of the module system. <br>
</p>
There are several changes in this update, JDK 9 b118 has the updated
policy for root modules described <br>
in JEP 261 [1]. This means that java.corba and the 6 EE modules
aren't resolved by default and so it will <br>
look "as if" the types in these modules have been removed. More info
on the JDK 9 dev mailing list [2].<br>
<br>
A change that went into JDK 9 b102 is worth mentioning: <br>
JDK9: Remove stopThread RuntimePermission=C2=A0 from the default
java.policy In previous releases, untrusted=C2=A0 <br>
code had the "stopThread" RuntimePermission granted by default. This
permission allows untrusted code <br>
to call Thread.stop(), initiating an asynchronous ThreadDeath Error,
on threads in the same thread group. <br>
Having a ThreadDeath Error thrown asynchronously is not something
that trusted code should be expected <br>
to handle gracefully. The permission is no longer granted by
default.<br>
<font size=3D"+1"> </font>
<pre><font size=3D"+1">Rgds,Rory</font>
</pre>
<br>
[1] <a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext"
href=3D"http://openjdk.java.net/jeps/261">http://openjdk.java.net/j=
eps/261</a><br>
[2] <a class=3D"moz-txt-link-freetext"
href=3D"http://mail.openjdk.java.net/pipermail/jdk9-dev/2016-May/004309.h=
tml">http://mail.openjdk.java.net/pipermail/jdk9-dev/2016-May/004309.html=
</a><br>
<br>
<pre class=3D"moz-signature" cols=3D"72">--=20
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin,Ireland</pre>
</body>
</html>
--------------1766302E4CA621807F143591--
--===============1944648998116788894==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
--===============1944648998116788894==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Cruisecontrol-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-devel
--===============1944648998116788894==--