Java SE JSR 250 annotations module renamed to java.xml.ws.annotation?

[Alan Bateman]

On 13/02/2017 14:32, David M. Lloyd wrote:

> I think this is an error.  It makes more sense to have the 
> javax.annotation package exist in its own module.  If the long-idle 
> JSR 250 and specifications like it are really a concern, then this 
> module should follow the pattern of all other such modules and be 
> upgradeable.
It is its own module and it is upgradable.

>
> This once again shines a bright light on a few key Jigsaw defects, and 
> it's getting a bit frustrating watching requirements get reconned to 
> compensate for implementation problems.  This is purely a hack to make 
> up for an implementation difficulty and makes no sense when framed 
> from the perspective of the end user. Let's try to do better.
The technical debt here that a handful of APIs are "shared" between Java 
SE and Java EE. The first steps to addressing that technical debt are in 
the JSR 379 EDR.

-Alan.