Track GraalVM as a deployment environment

Note the incredible License restrictions which appear to say that we need to read all of the code before we can know whether it is safe to use this. So this isn't a deployable thing but might be something we might want to let people know they might want to use if they wanted to live on the bleeding edge.

I did a quick smoke test on the Java 11 stack with Graal 20... with the predictable result that most things failed at some point because of the scripting engine differences. In the Java 11 stack, this includes java-support which I guess has grown some more functionality in this area.

If we wanted to make progress from here we'd need to provide some sort of test support that figured out what to do depending on the runtime environment. We might need that in any case for the Nashorn transition, see JPAR-121.

Graal 20 is out. This is available in both Java 8 and Java 11 flavours. Windows is now out of "experimental" but still seems a bit behind. Linux/ARM is "experimental".

Things are now split into "Community" and "Enterprise" editions. Community is free for any use; Enterprise is free for evaluation but a paid product on top of an Oracle Java SE subscription running at an additional £170pa per seat.

The Enterprise edition "provides additional performance, security, and scalability relevant for running applications in production".

Quick smoke test as of 2019-05-13 of Java 7 platform projects:

• java-support seems OK

• spring-extensions has test issues around runnable resources

• java-metadata-aggregator seems OK

• java-opensaml has test issues around scripted functions

• java-identity-provider has test issues around scripted functions

None of this is surprising, as GraalVM includes a new JavaScript engine (see ).

Obviously can't test anything from the Java 11 platform yet.