Another temporary javac hack please

[Mark Reinhold]

I need to be able to write module-info files like this:

    module demo @ 0.1 {
	requires jdk.base @ 7-ea;
    }

Right now the above declaration causes javac to look for a jdk.base
module in the module path, and naturally it doesn't find one.  That
will change over time, but for now javac is getting all JDK classes
from the usual boot class path.

For demo purposes I need to write such declarations in source files
and interpret them at install time.  Would it make sense to add
another short-term hack which would cause javac to avoid interpreting
dependences upon any "platform" module, but still pass them through
to the resulting module-info.class file?

Thanks,
- Mark