Scripting engines in V2 distribution

[Cantor, Scott]

An outstanding question for the 2.4 release is whether to keep shipping
the scripting engines for beanshell, jruby, jython, groovy, and javascript.

Chad originally included them because he recompiled them from the old
scripting.dev.java.net site for Java 1.5 along with the scripting API
itself.

We no longer build for Java 1.5, and the part of the core code that
supports scripting with the default scripting engine (the Rhino Javascript
engine) is part of Java 1.6.

My discomfort with the scripting jars is that they don't have any sort of
active development or official release status behind them. The old web
sites are renamed, there are broken links everywhere, and their subversion
has no tags for the engines and no check-ins for years. This is not the
kind of code I tend to ship or depend on in the SP, so I'm bringing the
same discomfort to the IdP.

We could leave things be for 2.4 and just pull them in V3, or we can pull
them for 2.4 and just get it over with. The impact is that anybody using a
non-default scripting engine would just be responsible for going and
getting/building the engine they think is still viable to depend on (I
would personally claim none of them are based on my observations, but
perhaps I'm wrong).

Of course one could easily just copy the jars we were shipping into one's
system rather than going and building them by hand.

I don't know how much use there is of any of these engines. I doubt it's
widespread.

-- Scott