JMH and JDK9

[Christian Thalinger]

> On Mar 31, 2016, at 9:57 PM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> 
> 
> On 01/04/2016 02:01, Christian Thalinger wrote:
>> Maybe totally unrelated but I’m seeing these exceptions with Eclipse 4.6M6:
>> 
>> 
> I don't recognize this but there has been at least one issue with Eclipse [1] where it needed a configuration change due to the ongoing effort to move non-core classes out of the boot loader.
> 
> In this case then the types are in module java.annotations.common. We moved those types to the extension class loader (now called the "platform class loader" btw) last year. In JDK 8 and older then the types in this module were defined to the boot loader. If changing the defining class loader is caused this then I would have expected we would have heard about it before now but perhaps there aren't too many people running Eclipse on the latest JDK 9 builds.
> 
> One other thing about these so-called "Common Annotations" is that Java SE only defines a small subset whereas Java EE defines all the annotations that JSR-250 defined. If they have been putting the EE version on the class path then it's not going to work now because we can't split packages between the class path and modules. The way to upgrade is to deploy the EE version as a module on the "upgrade module path". I have no idea if they are using it of course but mentioning it in case it might be relevant.
> 
> Are you going to submit a bug to Eclipse on this?

My lack of understanding of the problem tells me no.  Maybe you should :-)

Btw. Eclipse 4.6M5 works fine.

> 
> -Alan
> 
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=466683 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=466683>