Rhino, Nashorn IdPV2 and Scripting

[Rod Widdowson]

> Since the jars here can basically be named anything, I suggest we rename
> them to something we can understand later.

Makes sense.
 
> I assume js.jar is the rhino implementation, and js-engine is the adapter
> that makes it a scripting engine?

Absolutely.  I should add that I did a brief eyeball of the code which makes
up js-engine and couldn't see any obvious nefarious behaviour.

> I'm not clear on how the JDK version is a factor, is it that you targeted
> JDK8 with the compile so it doesn't run on JDK6?

I compiled it with JDK7 for the only reason that that is what I had as my
default JDK at that stage.  In theory it can be compiled with JDK6 and
deployed against same, but when I did that Liam had some issues with things
not working as expected.  I have not chased this up, but it was something to
do with the built in libraries (JSON not found).  I fear that there may be
classpath overlaps between those classes inside the Mozilla supplied js.jar
and those inside the rhino implementation which comes with the JRE.

> Do we just want to do a version built with JDK6 that will run on any of
> them?

I certainly could, but our only interesting use-case is to run against a V8
JVM.  I'd rather not get into the case of having to support people running a
non-standard scripting engine on anything other than JRE8;  this is
particularly true given the bad experiences that Liam had with running it
against V6.

Rod