On 22/04/2016 20:01, Sanne Grinovero wrote:
:
Thanks! Indeed, it's working great.
[tested 9-ea+114-2016-04-19-162931.javare.4880.nc]
Ironically this means we can make more progress testing using the
Jigsaw EA builds, while I'm completely blocked on the "mainline".
Thanks for confirming.
W
o: Alan Bateman
> Cc: jigsaw-dev; hotspot-dev Source Developers
> Subject: Re: JMH and JDK9
>
> On Tue, Apr 5, 2016 at 3:16 PM, Andrew Dinn wrote:
>> On 05/04/16 11:17, Alan Bateman wrote:
>> . . .
>>> We recently updated JEP 261 proposing that "java
On Wed, Apr 20, 2016 at 1:57 PM, Alan Bateman wrote:
>
> (dropping hotspot-dev and change the subject line as this discussion thread
> has moved on)
>
> On 20/04/2016 13:28, Sanne Grinovero wrote:
>>
>> :
>> Agreed: excellent idea!
>>
>> I'm eager to try it out so that we can resume testing of eve
-dev; hotspot-dev Source Developers
Subject: Re: JMH and JDK9
On Tue, Apr 5, 2016 at 3:16 PM, Andrew Dinn wrote:
> On 05/04/16 11:17, Alan Bateman wrote:
> . . .
>> We recently updated JEP 261 proposing that "java.se" be the only
>> java.* root module that is resolve
(dropping hotspot-dev and change the subject line as this discussion
thread has moved on)
On 20/04/2016 13:28, Sanne Grinovero wrote:
:
Agreed: excellent idea!
I'm eager to try it out so that we can resume testing of everything
else too; I just tried my luck with build 9-ea+114 but it didn't
On Tue, Apr 5, 2016 at 3:16 PM, Andrew Dinn wrote:
> On 05/04/16 11:17, Alan Bateman wrote:
> . . .
>> We recently updated JEP 261 proposing that "java.se" be the only java.*
>> root module that is resolved when compiling code in the unnamed module
>> or at runtime when the main class is loaded
On 05/04/16 11:17, Alan Bateman wrote:
. . .
> We recently updated JEP 261 proposing that "java.se" be the only java.*
> root module that is resolved when compiling code in the unnamed module
> or at runtime when the main class is loaded from the class path [1]. On
> the surface then it will "app
On 05/04/2016 10:25, Andrew Dinn wrote:
:
This is actually one example of a more general problem where both Java
EE components and Java EE applications need to employ classes which
extend the class set of a package currently bundled in a Jigsaw module.
For example, as well as the common annotati
