modulepath and classpath mixture

[Paul Benedict]

I have an idea:

What if the jar tool in JDK 9 was upgraded so that the Manifest had a new
entry that contained the module name? This would allow access to it without
requiring new API, and tools running JDK 8 or below would have an easy way
to detect if the JAR is a module.

And is there a secondary benefit to decoupling the module name and the
module configuration? I'd like to hear another use case, if one exists.

On 08/03/2016 20:06, Paul Benedict wrote:
> >* Robert, it's sounds like a chicken-and-egg problem. You need the module
> *>* name to compile but don't know it until you have compiled.
> *>I think the scenario is where the module has been compiled and the issue
> is the separate compilation of the tests "as if" they are in the module.
>
> -Alan
>
>
Cheers,
Paul