I don’t believe they are removing ScriptEngine support, only the JavaScript
engine being there by default. I wouldn’t have recommended using it anyway
since it doesn’t compile the scripts.
Ralph
> On Jul 2, 2018, at 8:25 AM, Matt Sicker wrote:
>
> On Mon, 2 Jul 2018 at 04:29, Rory O'Donnell
On Mon, 2 Jul 2018 at 04:29, Rory O'Donnell
wrote:
> * 335: *Deprecate the Nashorn JavaScript Engine*
>
Hooray, more built in features going away! So first we have the issue of
XML APIs being removed from the base (which, as far as I can tell, means
you either have to add special command line
Hi all,
I've found another reusable message memory leak[1]. I've pushed a
proposed fix[2] which adds a new "Clearable" interface we can use to
reset reusable messages. Ideally this would be a default method on
ReusableMessage, however I would like to get this fix into 2.11.1 so
I've made the inter
Hi Ralph,
*JDK 11 is now in Rampdown Phase one***
The overall feature set is frozen. No further JEPs will be targeted to
this release.We’ve forked the main-line source repository, jdk/jdk, to
the jdk/jdk11 stabilization repository. Any changes pushed to jdk/jdk or
jdk/client are now bound for
