How to actually ship JSR-250?

Alan Bateman Alan.Bateman at
Thu Apr 20 13:18:25 UTC 2017

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 module such 
> that can see it, *and* I have my proper 
> java.annotations.common module name?  Am I forced to ship my 
> annotations module as  Or manually replace 
> with one that looks for my annotations (and where does 
> that leave the original module)?
> is upgradable so all you need to do is deploy the 
compiled form of the following on the upgrade module path:

module {
     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 
"", maybe something else.


More information about the jigsaw-dev mailing list