Question about FileManagers in Jigsaw.
Alan.Bateman at oracle.com
Tue Mar 13 08:47:21 PDT 2012
On 13/03/2012 14:52, Fredrik Öhrström wrote:
> Ok, see if I got this right:
> We need a boot-jdk compatible: 2xboostrap_javac, bootstrap_jpkg (jpkg is
> used to create jmod files, right?)
> (but not bootstrap_jmod? (jmod is used to install jmod files into the
> jvm, right?)
> We do not really need to build a full launcher for the bootstrap jpkg do
> we? We can just run the classes directly?
jmod is the tool that creates the module library so it's needed to
create an image, even a minimal image that only contains the base
module. It can also install modules where the classes are in module path
layout, which is likely to be useful.
I suspect that jpkg may not be critical for the bootstrapping, but
clearly important for later when the build creates the native and jmod
Jon is the best person to consult with on the sequencing. I think that
one possible approach is to use the bootstrap JDK + javac (with some
Jigsaw emulation) to compile the base module and then run in module mode
to get us to an initial module image. Once we have an image with the
base + langtools modules installed then it should be easier sailing.
> Then we generate Java sources for Charsets et al.
> Next step is to build the base module from shuffled (multi module)
> sourcepath using the second
> bootstrap_javac? Or could we just compile the whole jdk using multi
> module compile?
> It seems like that should be possible?
I think this would be desirable, assuming that shuffled means the module
path layout that javac understands.
> Moving the jaxp, jaxws and corba into the jdk build makes sense even
> without jigsaw.
I don't know the history as to why as to why the bootstrap JDK is used
for these repos.
More information about the jigsaw-dev