How to actually ship JSR-250?

[David M. Lloyd]

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 JDK's java.xml.ws.annotation module such
>> that java.xml.ws can see it, *and* I have my proper
>> java.annotations.common module name?  Am I forced to ship my
>> annotations module as java.xml.ws.annotation?  Or manually replace
>> java.xml.ws with one that looks for my annotations (and where does
>> that leave the original java.xml.ws.annotation module)?
>>
> java.xml.ws.annotation is upgradable so all you need to do is deploy the
> compiled form of the following on the upgrade module path:
>
> module java.xml.ws.annotation {
>     requires transitive java.annotations.common;
> }
>
> Separately, I don't know what name that JSR-250 will eventually choose.
> It could be indeed be "java.annotations.common", maybe
> "java.ee.annotation", maybe something else.

I'm not too worried about that; it has to be decided by the time of Java 
EE 9 (obviously) but until then I just want to ensure that it is 
definitely possible to do this, as (unless I missed something) I don't 
believe that it was adequately covered in prior discussions.

-- 
- DML