| Re: [ease-dev] Nashorn removal in OpenJDK |
|
I do not know how trace compass selects script engines. Probably it works out of the biox when the Rhino engine is installed from the EASE update sites. If not, please ask on the trace
compass mailing list. Christian From: ease-dev <ease-dev-bounces@xxxxxxxxxxx>
On Behalf Of Bernd Hufmann via ease-dev
Hi Christian thanks for the answer. I don't know what the steps are to use the Mozilla engine in my Eclipse Trace Compass RCP? Could you please provide me some pointers on how to make
it work? BR Bernd
From: ease-dev <ease-dev-bounces@xxxxxxxxxxx> on behalf of
Christian.Pontesegger@xxxxxxxxxxxx <Christian.Pontesegger@xxxxxxxxxxxx> Hi Bernd, we support Mozilla Rhino [1] since the first release and will continue to do so. Actually Rhino was always my preferred engine due to its debug functionality. Nashorn will stay around @EASE as long as Eclipse base requirements will enable us to use Nashorn. Currently this is Java 11, which is fine, but I guess with Java 17 on the road this will change. HTH Christian [1]
https://github.com/mozilla/rhino From: ease-dev <ease-dev-bounces@xxxxxxxxxxx>
On Behalf Of Bernd Hufmann via ease-dev
Hello, The JS scripting engine Nashorn was removed starting from OpenJDK version 15. With this removal EASE scripting with _javascript_ won't work anymore, because
of missing _javascript_ engines. Some Eclipse projects will require Java 17 starting with simultaneous release 2022-12, for example Eclipse CDT project. Trace Compass is using EASE scripting
and due some dependencies it will require to run with Java 17 and hence the EASE scripting support in Trace Compass with JS won't work anymore. Are there any plans from the EASE project to provide an updated or new _javascript_ engine for Java version >= Java 15? And any suggestions on how to overcome
this issue? Please let me know. Thanks Bernd |