-
From: David M. Lloyd [mailto:david.ll...@redhat.com]
Sent: Thursday, April 20, 2017 6:49 PM
To: Stephen Felts; Alan Bateman; jigsaw-dev
Subject: Re: How to actually ship JSR-250?
To address the first point only... I think if Java EE 8 required Java SE 9,
that would be surprising news for all
To: Alan Bateman; jigsaw-dev
Subject: Re: How to actually ship JSR-250?
On 04/20/2017 08:18 AM, Alan Bateman wrote:
On 20/04/2017 13:57, David M. Lloyd wrote:
Let's say I want to create a module distribution with my own JSR 250
classes. Let's also assume that I or the spec team want the module
the
module path, the module path wins?
-Original Message-
From: David M. Lloyd [mailto:david.ll...@redhat.com]
Sent: Thursday, April 20, 2017 9:21 AM
To: Alan Bateman; jigsaw-dev
Subject: Re: How to actually ship JSR-250?
On 04/20/2017 08:18 AM, Alan Bateman wrote:
> On 20/04/2017 13
On 04/20/2017 08:18 AM, Alan Bateman wrote:
On 20/04/2017 13:57, David M. Lloyd wrote:
Let's say I want to create a module distribution with my own JSR 250
classes. Let's also assume that I or the spec team want the module to
be named java.annotations.common.
How do I properly upgrade the
On 20/04/2017 13:57, David M. Lloyd wrote:
Let's say I want to create a module distribution with my own JSR 250
classes. Let's also assume that I or the spec team want the module to
be named java.annotations.common.
How do I properly upgrade the JDK's java.xml.ws.annotation module such
Let's say I want to create a module distribution with my own JSR 250
classes. Let's also assume that I or the spec team want the module to
be named java.annotations.common.
How do I properly upgrade the JDK's java.xml.ws.annotation module such
that java.xml.ws can see it, *and* I have my
