Scripting engines in V2 distribution

[Cantor, Scott]

On 4/1/13 12:58 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>
>The latest version of Groovy 2.1.2 does seem to have this support in
>their 'groovy-jsr223-2.1.2.jar' which contains what (I would think) are
>the expected classes, based on their names.
>
>Tracking down JRuby was a little harder, but I did find their Jira issue
>[2] where they discussed this, and it looks like they did the same.  The
>JRuby source tree and jruby.jar binary does seem to have the expected
>content, including the Services API declaration
> for javax.script.ScriptEngineFactory.

Ok. That makes a lot more sense, but reinforces that us shipping an
ancient copy from a dead source is probably a bad idea.

>Now, whether we should start and/or continue shipping any of the
>particular languages/engines in the IdP, as opposed to asking the
>deployer to install what they want, is another (and different) question.

Even if we did, it seems clear we'd want to get them from the proper
sources. I'm much more willing to consider that, but since I think the
engines are probably somewhat coupled to the language jars from a
versioning standpoint, that seems like a bad idea.

And I think Peter's observation about jython was that even though we ship
jython-engine, that doesn't give you jython support until you add the rest
of the code, I guess. I had assumed the engines were self-contained, but
clearly not.

So seems this is pointless for us to keep including in the current form.

-- Scott