Re: JDK 10 entered Rampdown Phase One on 14th of December

2018-01-19 Thread Mark Thomas 
On 19/01/2018 14:36, Rory O'Donnell wrote:
> Mark,
> 
> Daniel has replied to the thread.

Tx. Composing a response now.

Mark


> 
> Rgds,Rory
> 
> 
> On 19/01/2018 13:59, Mark Thomas wrote:
>> On 19/01/18 12:41, Mark Thomas wrote:
>>> On 19/01/18 12:26, Rory O'Donnell wrote:
 Hi Mark,

 There is a discussion on possible fix/solution for JDK-8195096
  at:

 http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-January/050989.html



 Can you add your comments/suggestions there ?
>>> Sure. I'll do that shortly.
>> I'd like to reply to the right thread but I can't do that as I wasn't
>> subscribed to the list when the last message in the thread was sent.
>> Could you ping that thread with something short so I can then reply
>> properly? A simple "I've pinged the Tomcat folks for their input" or
>> something along those lines should be sufficient.
>>
>> I could just post to the list but I'd rather do it on the right thread.
>>
>> Thanks,
>>
>> Mark
>>
>>
>>
>>> Mark
>>>
>>>
 Rgds, Rory


 On 12/01/2018 13:17, Rory O'Donnell wrote:
> Hi Mark
>
> How serious is this issue ?
>
> It's logged with a low priority, it might have to wait for JDK 11.
>
> Rgds,Rory
>
>
>
> On 12/01/2018 11:39, Rory O'Donnell wrote:
>> Hi Mark,
>>
>> Thanks for the feedback, I'll pass it on.
>>
>> Rgds,Rory
>>
>>
>> On 12/01/2018 10:20, Mark Thomas wrote:
>>> On 18/12/17 09:56, Rory O'Donnell wrote:
>>>
>>> 
>>>
 *Feedback* - If you have suggestions or encounter bugs, please
 submit
 them using the usual Java SE bug-reporting channel.
 Be sure to include complete version information from the output
 of the
 |java --version| command.
>>> Hi,
>>>
>>> I did some testing on this today. I found a problem with our custom
>>> LogManager triggered by some fixes to the JRE LogManager.
>>>
>>> I've created a report via the standard mechanism as requested. The
>>> internal review ID is 9052225. Anything you can do to get this in
>>> front
>>> of the right folks to ensure it doesn't get overlooked would be
>>> appreciated.
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>> -
>>>
>>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>>
> 


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: JDK 10 entered Rampdown Phase One on 14th of December

2018-01-19 Thread Rory O'Donnell 

Mark,

Daniel has replied to the thread.

Rgds,Rory


On 19/01/2018 13:59, Mark Thomas wrote:

On 19/01/18 12:41, Mark Thomas wrote:

On 19/01/18 12:26, Rory O'Donnell wrote:

Hi Mark,

There is a discussion on possible fix/solution for JDK-8195096
 at:

http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-January/050989.html


Can you add your comments/suggestions there ?

Sure. I'll do that shortly.

I'd like to reply to the right thread but I can't do that as I wasn't
subscribed to the list when the last message in the thread was sent.
Could you ping that thread with something short so I can then reply
properly? A simple "I've pinged the Tomcat folks for their input" or
something along those lines should be sufficient.

I could just post to the list but I'd rather do it on the right thread.

Thanks,

Mark




Mark



Rgds, Rory


On 12/01/2018 13:17, Rory O'Donnell wrote:

Hi Mark

How serious is this issue ?

It's logged with a low priority, it might have to wait for JDK 11.

Rgds,Rory



On 12/01/2018 11:39, Rory O'Donnell wrote:

Hi Mark,

Thanks for the feedback, I'll pass it on.

Rgds,Rory


On 12/01/2018 10:20, Mark Thomas wrote:

On 18/12/17 09:56, Rory O'Donnell wrote:




*Feedback* - If you have suggestions or encounter bugs, please submit
them using the usual Java SE bug-reporting channel.
Be sure to include complete version information from the output of the
|java --version| command.

Hi,

I did some testing on this today. I found a problem with our custom
LogManager triggered by some fixes to the JRE LogManager.

I've created a report via the standard mechanism as requested. The
internal review ID is 9052225. Anything you can do to get this in front
of the right folks to ensure it doesn't get overlooked would be
appreciated.

Thanks,

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin,Ireland


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: JDK 10 entered Rampdown Phase One on 14th of December

2018-01-19 Thread Rory O'Donnell 

I'll ask Daniel to reply.

Rgds,Rory


On 19/01/2018 13:59, Mark Thomas wrote:

On 19/01/18 12:41, Mark Thomas wrote:

On 19/01/18 12:26, Rory O'Donnell wrote:

Hi Mark,

There is a discussion on possible fix/solution for JDK-8195096
 at:

http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-January/050989.html


Can you add your comments/suggestions there ?

Sure. I'll do that shortly.

I'd like to reply to the right thread but I can't do that as I wasn't
subscribed to the list when the last message in the thread was sent.
Could you ping that thread with something short so I can then reply
properly? A simple "I've pinged the Tomcat folks for their input" or
something along those lines should be sufficient.

I could just post to the list but I'd rather do it on the right thread.

Thanks,

Mark




Mark



Rgds, Rory


On 12/01/2018 13:17, Rory O'Donnell wrote:

Hi Mark

How serious is this issue ?

It's logged with a low priority, it might have to wait for JDK 11.

Rgds,Rory



On 12/01/2018 11:39, Rory O'Donnell wrote:

Hi Mark,

Thanks for the feedback, I'll pass it on.

Rgds,Rory


On 12/01/2018 10:20, Mark Thomas wrote:

On 18/12/17 09:56, Rory O'Donnell wrote:




*Feedback* - If you have suggestions or encounter bugs, please submit
them using the usual Java SE bug-reporting channel.
Be sure to include complete version information from the output of the
|java --version| command.

Hi,

I did some testing on this today. I found a problem with our custom
LogManager triggered by some fixes to the JRE LogManager.

I've created a report via the standard mechanism as requested. The
internal review ID is 9052225. Anything you can do to get this in front
of the right folks to ensure it doesn't get overlooked would be
appreciated.

Thanks,

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin,Ireland


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: JDK 10 entered Rampdown Phase One on 14th of December

2018-01-19 Thread Mark Thomas 
On 19/01/18 12:41, Mark Thomas wrote:
> On 19/01/18 12:26, Rory O'Donnell wrote:
>> Hi Mark,
>>
>> There is a discussion on possible fix/solution for JDK-8195096
>>  at:
>>
>> http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-January/050989.html
>>
>>
>> Can you add your comments/suggestions there ?
> 
> Sure. I'll do that shortly.

I'd like to reply to the right thread but I can't do that as I wasn't
subscribed to the list when the last message in the thread was sent.
Could you ping that thread with something short so I can then reply
properly? A simple "I've pinged the Tomcat folks for their input" or
something along those lines should be sufficient.

I could just post to the list but I'd rather do it on the right thread.

Thanks,

Mark



> 
> Mark
> 
> 
>>
>> Rgds, Rory
>>
>>
>> On 12/01/2018 13:17, Rory O'Donnell wrote:
>>> Hi Mark
>>>
>>> How serious is this issue ?
>>>
>>> It's logged with a low priority, it might have to wait for JDK 11.
>>>
>>> Rgds,Rory
>>>
>>>
>>>
>>> On 12/01/2018 11:39, Rory O'Donnell wrote:
 Hi Mark,

 Thanks for the feedback, I'll pass it on.

 Rgds,Rory


 On 12/01/2018 10:20, Mark Thomas wrote:
> On 18/12/17 09:56, Rory O'Donnell wrote:
>
> 
>
>> *Feedback* - If you have suggestions or encounter bugs, please submit
>> them using the usual Java SE bug-reporting channel.
>> Be sure to include complete version information from the output of the
>> |java --version| command.
> Hi,
>
> I did some testing on this today. I found a problem with our custom
> LogManager triggered by some fixes to the JRE LogManager.
>
> I've created a report via the standard mechanism as requested. The
> internal review ID is 9052225. Anything you can do to get this in front
> of the right folks to ensure it doesn't get overlooked would be
> appreciated.
>
> Thanks,
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>

>>>
>>
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: JDK 10 entered Rampdown Phase One on 14th of December

2018-01-19 Thread Mark Thomas 
On 19/01/18 12:26, Rory O'Donnell wrote:
> Hi Mark,
> 
> There is a discussion on possible fix/solution for JDK-8195096
>  at:
> 
> http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-January/050989.html
> 
> 
> Can you add your comments/suggestions there ?

Sure. I'll do that shortly.

Mark


> 
> Rgds, Rory
> 
> 
> On 12/01/2018 13:17, Rory O'Donnell wrote:
>> Hi Mark
>>
>> How serious is this issue ?
>>
>> It's logged with a low priority, it might have to wait for JDK 11.
>>
>> Rgds,Rory
>>
>>
>>
>> On 12/01/2018 11:39, Rory O'Donnell wrote:
>>> Hi Mark,
>>>
>>> Thanks for the feedback, I'll pass it on.
>>>
>>> Rgds,Rory
>>>
>>>
>>> On 12/01/2018 10:20, Mark Thomas wrote:
 On 18/12/17 09:56, Rory O'Donnell wrote:

 

> *Feedback* - If you have suggestions or encounter bugs, please submit
> them using the usual Java SE bug-reporting channel.
> Be sure to include complete version information from the output of the
> |java --version| command.
 Hi,

 I did some testing on this today. I found a problem with our custom
 LogManager triggered by some fixes to the JRE LogManager.

 I've created a report via the standard mechanism as requested. The
 internal review ID is 9052225. Anything you can do to get this in front
 of the right folks to ensure it doesn't get overlooked would be
 appreciated.

 Thanks,

 Mark

 -
 To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: dev-h...@tomcat.apache.org

>>>
>>
> 


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: JDK 10 entered Rampdown Phase One on 14th of December

2018-01-19 Thread Rory O'Donnell 

Hi Mark,

There is a discussion on possible fix/solution for JDK-8195096 
 at:


http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-January/050989.html

Can you add your comments/suggestions there ?

Rgds, Rory


On 12/01/2018 13:17, Rory O'Donnell wrote:

Hi Mark

How serious is this issue ?

It's logged with a low priority, it might have to wait for JDK 11.

Rgds,Rory



On 12/01/2018 11:39, Rory O'Donnell wrote:

Hi Mark,

Thanks for the feedback, I'll pass it on.

Rgds,Rory


On 12/01/2018 10:20, Mark Thomas wrote:

On 18/12/17 09:56, Rory O'Donnell wrote:




*Feedback* - If you have suggestions or encounter bugs, please submit
them using the usual Java SE bug-reporting channel.
Be sure to include complete version information from the output of the
|java --version| command.

Hi,

I did some testing on this today. I found a problem with our custom
LogManager triggered by some fixes to the JRE LogManager.

I've created a report via the standard mechanism as requested. The
internal review ID is 9052225. Anything you can do to get this in front
of the right folks to ensure it doesn't get overlooked would be 
appreciated.


Thanks,

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org







--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin,Ireland

Re: JDK 10 entered Rampdown Phase One on 14th of December

2018-01-15 Thread Mark Thomas 
FYI:

The bug was accepted:
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8195096


On 12/01/18 13:28, Mark Thomas wrote:
> On 12/01/18 13:17, Rory O'Donnell wrote:
>> Hi Mark
>>
>> How serious is this issue ?
> 
> Hi,
> 
> In terms of functionality, it isn't serious. As far as I can tell, there
> are no functional side-effects for Tomcat.
> 
> However, the more I think about this, the more serious an issue I think
> this will be. A large percentage of Tomcat users operate in environments
> where any logging that even hints that something isn't right has to be
> addressed. A stack trace to stdout would certainly get their attention.
> 
> I think we need a way to suppress this message. Without it a large
> proportional Tomcat users won't be allowed by organisational policy to
> run Tomcat on JDK 10. "Trust us. You can ignore that stack trace, it is
> a known issue with Java 10 that doesn't cause any harm." isn't going to
> be enough for most users.
> 
> My preference remains making that method protected so we can override it
> and make it a NO-OP (Tomcat's custom LogManager handles this already).
> However, I'd settle for anything that enabled that message to be suppressed.
> 
>> It's logged with a low priority, it might have to wait for JDK 11.
> 
> Understood.
> 
> Cheers,
> 
> Mark
> 
> 
>>
>> Rgds,Rory
>>
>>
>>
>> On 12/01/2018 11:39, Rory O'Donnell wrote:
>>> Hi Mark,
>>>
>>> Thanks for the feedback, I'll pass it on.
>>>
>>> Rgds,Rory
>>>
>>>
>>> On 12/01/2018 10:20, Mark Thomas wrote:
 On 18/12/17 09:56, Rory O'Donnell wrote:

 

> *Feedback* - If you have suggestions or encounter bugs, please submit
> them using the usual Java SE bug-reporting channel.
> Be sure to include complete version information from the output of the
> |java --version| command.
 Hi,

 I did some testing on this today. I found a problem with our custom
 LogManager triggered by some fixes to the JRE LogManager.

 I've created a report via the standard mechanism as requested. The
 internal review ID is 9052225. Anything you can do to get this in front
 of the right folks to ensure it doesn't get overlooked would be
 appreciated.

 Thanks,

 Mark

 -
 To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: dev-h...@tomcat.apache.org

>>>
>>
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: JDK 10 entered Rampdown Phase One on 14th of December

2018-01-12 Thread Mark Thomas 
On 12/01/18 13:17, Rory O'Donnell wrote:
> Hi Mark
> 
> How serious is this issue ?

Hi,

In terms of functionality, it isn't serious. As far as I can tell, there
are no functional side-effects for Tomcat.

However, the more I think about this, the more serious an issue I think
this will be. A large percentage of Tomcat users operate in environments
where any logging that even hints that something isn't right has to be
addressed. A stack trace to stdout would certainly get their attention.

I think we need a way to suppress this message. Without it a large
proportional Tomcat users won't be allowed by organisational policy to
run Tomcat on JDK 10. "Trust us. You can ignore that stack trace, it is
a known issue with Java 10 that doesn't cause any harm." isn't going to
be enough for most users.

My preference remains making that method protected so we can override it
and make it a NO-OP (Tomcat's custom LogManager handles this already).
However, I'd settle for anything that enabled that message to be suppressed.

> It's logged with a low priority, it might have to wait for JDK 11.

Understood.

Cheers,

Mark


> 
> Rgds,Rory
> 
> 
> 
> On 12/01/2018 11:39, Rory O'Donnell wrote:
>> Hi Mark,
>>
>> Thanks for the feedback, I'll pass it on.
>>
>> Rgds,Rory
>>
>>
>> On 12/01/2018 10:20, Mark Thomas wrote:
>>> On 18/12/17 09:56, Rory O'Donnell wrote:
>>>
>>> 
>>>
 *Feedback* - If you have suggestions or encounter bugs, please submit
 them using the usual Java SE bug-reporting channel.
 Be sure to include complete version information from the output of the
 |java --version| command.
>>> Hi,
>>>
>>> I did some testing on this today. I found a problem with our custom
>>> LogManager triggered by some fixes to the JRE LogManager.
>>>
>>> I've created a report via the standard mechanism as requested. The
>>> internal review ID is 9052225. Anything you can do to get this in front
>>> of the right folks to ensure it doesn't get overlooked would be
>>> appreciated.
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>>>
>>
> 


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: JDK 10 entered Rampdown Phase One on 14th of December

2018-01-12 Thread Rory O'Donnell 

Hi Mark

How serious is this issue ?

It's logged with a low priority, it might have to wait for JDK 11.

Rgds,Rory



On 12/01/2018 11:39, Rory O'Donnell wrote:

Hi Mark,

Thanks for the feedback, I'll pass it on.

Rgds,Rory


On 12/01/2018 10:20, Mark Thomas wrote:

On 18/12/17 09:56, Rory O'Donnell wrote:




*Feedback* - If you have suggestions or encounter bugs, please submit
them using the usual Java SE bug-reporting channel.
Be sure to include complete version information from the output of the
|java --version| command.

Hi,

I did some testing on this today. I found a problem with our custom
LogManager triggered by some fixes to the JRE LogManager.

I've created a report via the standard mechanism as requested. The
internal review ID is 9052225. Anything you can do to get this in front
of the right folks to ensure it doesn't get overlooked would be 
appreciated.


Thanks,

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org





--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin,Ireland


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: JDK 10 entered Rampdown Phase One on 14th of December

2018-01-12 Thread Rory O'Donnell 

Hi Mark,

Thanks for the feedback, I'll pass it on.

Rgds,Rory


On 12/01/2018 10:20, Mark Thomas wrote:

On 18/12/17 09:56, Rory O'Donnell wrote:




*Feedback* - If you have suggestions or encounter bugs, please submit
them using the usual Java SE bug-reporting channel.
Be sure to include complete version information from the output of the
|java --version| command.

Hi,

I did some testing on this today. I found a problem with our custom
LogManager triggered by some fixes to the JRE LogManager.

I've created a report via the standard mechanism as requested. The
internal review ID is 9052225. Anything you can do to get this in front
of the right folks to ensure it doesn't get overlooked would be appreciated.

Thanks,

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: JDK 10 entered Rampdown Phase One on 14th of December

2018-01-12 Thread Mark Thomas 
On 18/12/17 09:56, Rory O'Donnell wrote:



> *Feedback* - If you have suggestions or encounter bugs, please submit
> them using the usual Java SE bug-reporting channel.
> Be sure to include complete version information from the output of the
> |java --version| command.

Hi,

I did some testing on this today. I found a problem with our custom
LogManager triggered by some fixes to the JRE LogManager.

I've created a report via the standard mechanism as requested. The
internal review ID is 9052225. Anything you can do to get this in front
of the right folks to ensure it doesn't get overlooked would be appreciated.

Thanks,

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

JDK 10 entered Rampdown Phase One on 14th of December

2017-12-18 Thread Rory O'Donnell 

 Hi Mark,

*JDK 10 entered Rampdown Phase One on Thursday, 14 December [1] *

 * The Rampdown Phase One process will be similar to that of JDK 9 [2].

*JDK 10 Early Access  build 36 is available at : - jdk.java.net/10/*

Notable changes since previous email.

*JEPS included **the last 3 builds:*
JDK-8192833  :This is 
the primary implementation subtask of JEP 322 - *Time-Based Release 
Versioning*
JDK-8189941  : 
Implementation JEP 312: Thread-local handshake
JDK-8186571  : 
Implementation: JEP 307: Parallel Full GC for G1
JDK-8190308  : 
Implementation: JEP 316: Heap Allocation on Alternative Memory Devices


*build 36
*JDK-8148421  : 
Transport Layer Security (TLS) Session Hash and Extended Master Secret 
Extension
JDK-5016517  : Replace 
plaintext passwords by hashed passwords for out-of-the-box JMX Agent


**

*build 35 *
JDK-8188870  - Bump 
classfile version number to 54
JDK-8185985  - HTML 
files in doc-files subdirectories are wrapped with standard javadoc 
decorations
JDK-8186535 *- *Remove 
deprecated pre-1.2 SecurityManager methods and fields


*build 34* - JDK-8024352 
 - MBeanOperationInfo 
accepts any int value as "impact"


*Bug fixes reported by Open Source Projects  
:*
JDK-8191078  : Wrong 
"Package not found" warning
JDK-8191636  : 
[Windows] jshell tool: Wrong character in /env class-path command 
crashes jshell
JDK-8191834  : 
Assigning a void expression to a "var" crashes the 
compiler
JDK-8182638  : 
[macosx] Active modal dialog is hidden by another non-active one
JDK-8043315  : Nimbus: 
Setting Nimbus.Overrides property affects custom keymap installation
JDK-8172244  : AIOOBE 
in KeyStore.getCertificateAlias on Windows
JDK-8180141  : Missing 
entry in LineNumberTable for break statement that jumps out of try-finall


JDK 10 Schedule, Status & Features are available [3]

*Feedback* - If you have suggestions or encounter bugs, please submit 
them using the usual Java SE bug-reporting channel.
Be sure to include complete version information from the output of the 
|java --version| command.


Regards,
Rory

[1] http://mail.openjdk.java.net/pipermail/jdk-dev/2017-December/000357.html
[2] http://openjdk.java.net/projects/jdk9/rdp-1
[3] http://openjdk.java.net/projects/jdk/10/

--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland