jmod problem

[Mark Reinhold]

> Date: Fri, 12 Mar 2010 11:47:29 -0800
> From: mandy.chung at sun.com

> On 03/12/10 11:03, Jonathan Gibbons wrote:
>> I'm not sure if there is some confusion here.  Mark asked if I was using
>> $OUTPUTDIR/bin/java to which I said I was using the j2sdk-image.  I was not
>> using $OUTPUTDIR directly, nor was I suggesting that we should install
>> modules directly in $OUTPUTDIR.  I was commenting on the behavior of jmod
>> in j2sdk-image, with respect to missing module images.
>> 
>> If the confusion is mine, I apologize. :-)
> 
> Sorry to confuse you.  I should have made it clear.
> 
> There are two different issues:
> 1. j2sdk-image doesn't have a system module library.
> 
> To address your comment, we can either remove jmod from j2sdk-image or output a
> helpful error message.

It seems simpler just to remove the Jigsaw tools from the legacy images.

> ...
> 
> 2. $OUTPUTDIR doesn't have the system module library, with the modules
> installed.
> 
> For now, $OUTPUTDIR/bin/jmod create -L lib doesn't work.
> 
> I agree that for our development use, it'll be valuable if $OUTPUTDIR/bin/jmod
> works and we can also run jtreg modules tests with $OUTPUTDIR as it is today.
> Until we have the zero mod library implemented (the idea you and Mark
> discussed) that can read modules from "modulepath" that no installation is
> required, we need to have the system module library in $OUTPUTDIR.

To clarify, "zero mod" in this context means something like the "zero
mod" facility now in javac, but implemented in the Java launcher so that
you can say something like

  $ java -L $OUTPUTDIR/mods MyUnitTest

rather than have to install a module into a library first just in order
to test it.

- Mark