Re: RFR [9] 8153737: Unsupported Module

2016-05-10 Thread Richard Opalka
On 05/10/2016 10:50 AM, Chris Hegarty wrote: On 9 May 2016, at 20:43, Richard Opalka wrote: Fixed in JBoss Marshalling upstream. Thanks for fixing this, and getting back to us on the list. I assume then that, at least, this part of JBoss is working on JDK 9 b115, right? Yes. Rio -Chris

Re: RFR [9] 8153737: Unsupported Module

2016-05-10 Thread Chris Hegarty
On 9 May 2016, at 20:43, Richard Opalka wrote: > Fixed in JBoss Marshalling upstream. Thanks for fixing this, and getting back to us on the list. I assume then that, at least, this part of JBoss is working on JDK 9 b115, right? -Chris. > Thanks, > > Rio > > On 04/27/2016 11:54 PM, Chris H

Re: RFR [9] 8153737: Unsupported Module

2016-05-09 Thread Richard Opalka
Fixed in JBoss Marshalling upstream. Thanks, Rio On 04/27/2016 11:54 PM, Chris Hegarty wrote: Hi Rio, We are missing sun/reflect/ReflectionFactory$GetReflectionFactoryAction inner class in jdk.unsupported module: java.lang.NoClassDefFoundError: sun/reflect/ReflectionFactory$GetReflectio

Re: RFR [9] 8153737: Unsupported Module

2016-04-27 Thread Chris Hegarty
Hi Rio, > We are missing sun/reflect/ReflectionFactory$GetReflectionFactoryAction inner > class > > in jdk.unsupported module: > > java.lang.NoClassDefFoundError: > sun/reflect/ReflectionFactory$GetReflectionFactoryAction >at > jdk.internal.loader.BuiltinClassLoader.loadClass(java.base@9

Re: RFR [9] 8153737: Unsupported Module

2016-04-27 Thread Richard Opalka
We are missing sun/reflect/ReflectionFactory$GetReflectionFactoryAction inner class in jdk.unsupported module: java.lang.NoClassDefFoundError: sun/reflect/ReflectionFactory$GetReflectionFactoryAction at jdk.internal.loader.BuiltinClassLoader.loadClass(java.base@9-internal/BuiltinClassLoad

Re: RFR [9] 8153737: Unsupported Module

2016-04-09 Thread Chris Hegarty
This change has been pushed to jdk9/dev. The hotspot gatekeeper will bring it down into the hotspot forests. -Chris. > On 7 Apr 2016, at 18:14, Chris Hegarty wrote: > > Enough technical debt has been paid down that we can now create the new > JDK-specific module as proposed by JEP 260 [1], name

Re: RFR [9] 8153737: Unsupported Module

2016-04-08 Thread Mandy Chung
> On Apr 8, 2016, at 8:35 AM, Chris Hegarty wrote: > > > I moved the tests from a directory named 'jdk.unsupported' to > unsupported', as other tests, in test/tools/jdeps/module, use > test/tools/jdeps as a test library, and the directory/test lib > name is conflicting with the module name. jtr

Re: RFR [9] 8153737: Unsupported Module

2016-04-08 Thread Chris Hegarty
On 08/04/16 03:52, Mandy Chung wrote: On Apr 7, 2016, at 10:14 AM, Chris Hegarty wrote: Enough technical debt has been paid down that we can now create the new JDK-specific module as proposed by JEP 260 [1], named jdk.unsupported. This module will initially contain, and export, the sun.misc p

Re: RFR [9] 8153737: Unsupported Module

2016-04-08 Thread Chris Hegarty
On 07/04/16 19:57, Alan Bateman wrote: On 07/04/2016 18:14, Chris Hegarty wrote: Enough technical debt has been paid down that we can now create the new JDK-specific module as proposed by JEP 260 [1], named jdk.unsupported. This module will initially contain, and export, the sun.misc package, an

Re: RFR [9] 8153737: Unsupported Module

2016-04-08 Thread Alan Bateman
On 08/04/2016 15:31, Peter Levart wrote: Will jdk.unsupported be "required public" by java.se? No because jdk.* are JDK-specific and should never be required by standard modules. Will you have to explicitly -addmodule jdk.unsupported for class-path programs too? It exports an API and the

Re: RFR [9] 8153737: Unsupported Module

2016-04-08 Thread Chris Hegarty
On 08/04/16 15:31, Peter Levart wrote: On 04/08/2016 12:24 PM, Paul Sandoz wrote: On 7 Apr 2016, at 19:14, Chris Hegarty wrote: Enough technical debt has been paid down that we can now create the new JDK-specific module as proposed by JEP 260 [1], named jdk.unsupported. This module will init

Re: RFR [9] 8153737: Unsupported Module

2016-04-08 Thread Peter Levart
On 04/08/2016 12:24 PM, Paul Sandoz wrote: On 7 Apr 2016, at 19:14, Chris Hegarty wrote: Enough technical debt has been paid down that we can now create the new JDK-specific module as proposed by JEP 260 [1], named jdk.unsupported. This module will initially contain, and export, the sun.misc

Re: RFR [9] 8153737: Unsupported Module

2016-04-08 Thread Paul Sandoz
> On 7 Apr 2016, at 19:14, Chris Hegarty wrote: > > Enough technical debt has been paid down that we can now create the new > JDK-specific module as proposed by JEP 260 [1], named jdk.unsupported. > This module will initially contain, and export, the sun.misc package, > and will eventually expor

Re: RFR [9] 8153737: Unsupported Module

2016-04-07 Thread Mandy Chung
> On Apr 7, 2016, at 10:14 AM, Chris Hegarty wrote: > > Enough technical debt has been paid down that we can now create the new > JDK-specific module as proposed by JEP 260 [1], named jdk.unsupported. > This module will initially contain, and export, the sun.misc package, > and will eventually e

Re: RFR [9] 8153737: Unsupported Module

2016-04-07 Thread Alan Bateman
On 07/04/2016 18:14, Chris Hegarty wrote: Enough technical debt has been paid down that we can now create the new JDK-specific module as proposed by JEP 260 [1], named jdk.unsupported. This module will initially contain, and export, the sun.misc package, and will eventually export the sun.reflect

RFR [9] 8153737: Unsupported Module

2016-04-07 Thread Chris Hegarty
Enough technical debt has been paid down that we can now create the new JDK-specific module as proposed by JEP 260 [1], named jdk.unsupported. This module will initially contain, and export, the sun.misc package, and will eventually export the sun.reflect package too ( once it has been sanitized ).