Question about FileManagers in Jigsaw.

[Jonathan Gibbons]

On 03/14/2012 08:28 AM, Alan Bateman wrote:
> On 13/03/2012 22:26, Jonathan Gibbons wrote:
>> :
>>
>>
>> So, here's what Mandy and I think we need:
>>
>> # start bootstrap
>> 1) Build hybrid/bootstrap javac using BOOTDIR javac on BOOTDIR java 
>> (includes zeromod + fake linking to jdk)
>>
>> # build minimal new JDK runtime
>> 2a) Compile Hotspot
>> 2b) Compile base module using hybrid/bootstrap javac on BOOTDIR java
>> 2c) Compile native libs for base module
>>
>> # build rest of JDK modules
>> 3a) Compile all other modules, including langtools, using 
>> hybrid/bootstrap javac on new JDK runtime in classpath mode
>> 3b) Compile native libs for each module
>>
>> # Dev usage
>> 4) Devs can work with and run the modules compiled in 2, 3 using 
>> modulepath
>>
>> # Product bits
>> 5) For final image, modules compiled in 2, 3 get converted to .jmod 
>> files and installed in library, using new jmod and jpkg on new JDK 
>> runtime
>>
>>
>> -- Jon
> Just catching up from yesterday.
>
> For the minimal runtime at step 2 then do you see this as a minimal 
> legacy or module runtime? Just thinking about legacy mode being 
> implemented with a jdk.legacy module under the covers.

Whatever necessary to support hybrid/bootstrap javac being able to run 
and have access to the Jigsaw module resolver.

>
> Also at 3a then I'm curious about compiling in classpath mode rather 
> than modulepath.

We cannot compile a module-info.java for hybrid/bootstrap javac using 
BOOTDIR javac.  If we were to use modulepath, we would need to add a 
step to use hybrid/bootstrap javac to compile its own module-info.java 
using either (BOOTDIR java + ZeroMod) or (minimal new runtime in 
classpath mode).

>
> -Alan.
>
>