jjs does not yet support module related options. So, user modules can
not be scripted directly with jjs as of now. Only way is to use to
launcher with -mp along with -m for jjs main class. With the change,
only module name needs to be specified.
Also, jjs tool is not shipped for embedded platforms (compact1). But,
jdk.nashorn.tools.Shell (used to be the jjs main in jdk8u) is compact1
compliant. So user can use
java -m jdk.scripting.nashorn
on embedded platforms [and use functionality reduced jjs there]
Yes, I tried to see if I can get it per-module config from somewhere -
but couldn't. I'm open to suggestions on how to do that in the current
scheme.
-Sundar
On 9/7/2016 5:48 PM, Alan Bateman wrote:
> On 07/09/2016 13:10, Sundararajan Athijegannathan wrote:
>
>> Please review http://cr.openjdk.java.net/~sundar/8165595/webrev.01/ for
>> https://bugs.openjdk.java.net/browse/JDK-8165595
>>
> I'm not sure that asking users to use -m is right here, esp. when the
> modules contains launchers. Also CreateJmods.gmk may not be the right
> place for this, it feels more like something that should be configured
> in a make file that is specific to the module.
>
>
> -Alan
