On 11.05.16 14:48, James Laskey wrote:
Wonder if we should have a configuration warning when an inappropriate version
is used.
+1, is it possible to implement?
Sent from my iPhone
On May 11, 2016, at 8:35 AM, Aleksey Shipilev
wrote:
On 05/11/2016 02:28 PM, Alan Bateman wrote:
On 11/0
Wonder if we should have a configuration warning when an inappropriate version
is used.
Sent from my iPhone
> On May 11, 2016, at 8:35 AM, Aleksey Shipilev
> wrote:
>
>> On 05/11/2016 02:28 PM, Alan Bateman wrote:
>>> On 11/05/2016 12:14, Aleksey Shipilev wrote:
>>> Got the same today, and f
On 05/11/2016 02:28 PM, Alan Bateman wrote:
> On 11/05/2016 12:14, Aleksey Shipilev wrote:
>> Got the same today, and figured it only fails with JDK 9 as the boot
>> JDK. Builds fine with JDK 8 as boot JDK. Filed:
>>https://bugs.openjdk.java.net/browse/JDK-8156740
>>
> You can never guarantee t
On 11/05/2016 12:14, Aleksey Shipilev wrote:
Got the same today, and figured it only fails with JDK 9 as the boot
JDK. Builds fine with JDK 8 as boot JDK. Filed:
https://bugs.openjdk.java.net/browse/JDK-8156740
You can never guarantee that the JDK N in development will build with a
older b
Got the same today, and figured it only fails with JDK 9 as the boot
JDK. Builds fine with JDK 8 as boot JDK. Filed:
https://bugs.openjdk.java.net/browse/JDK-8156740
Thanks,
-Aleksey
On 05/09/2016 05:07 PM, Jim Laskey (Oracle) wrote:
> Mac OS X - reproducible with a clean repo.
>
>
>> On May
Mac OS X - reproducible with a clean repo.
> On May 9, 2016, at 10:08 AM, Jim Laskey (Oracle)
> wrote:
>
>
>
>
> Generating blacklisted certs
> java.lang.ClassNotFoundException: sun.text.resources.BreakIteratorRules
> at
> jdk.internal.loader.BuiltinClassLoader.loadClass(java.base@9-
