No deps on JAXP was: JDK support for VM to read classes from modules in a module library

Alan Bateman Alan.Bateman at oracle.com
Mon May 21 01:03:51 PDT 2012


On 18/05/2012 08:07, Jaroslav Tulach wrote:
> :
>
> To give old schoolers equivalent "use" experience with JDK8 as they used to
> have with JDK7, I think it is enough to have one "JavaSE at 8.0" module with
> convenient dependencies which those guys can depend on. As far as I understand
> this is the Jigsaw plan, so balance between use and re-use should be there.
>
In the current builds then you'll see modules jdk at 8-ea and jdk.jre at 8-ea. 
These are aggregator modules and they re-export the APIs to give us the 
equivalent of the JDK and JRE. There are a couple of differences/issues 
but it essentially means that someone can require jdk.jre to ensure that 
all modules that comprise Java SE are present. I don't know what the 
ultimate names will be but one could envisage the jdk.jre be named to 
"java" or having the alias "java" so that applications can require 
java>=8. Note that this isn't the default at this time. The default for 
modules that don't express a synthesized dependency on "java.base", a 
module that comprise the core APIs. This means that applications or 
libraries built as modules that require anything more will need to 
specify their dependencies.

-Alan.



More information about the jigsaw-dev mailing list