Closed white-gecko closed 4 months ago
I've had a go on this on the branch named explicit_include_nashorn. Which isn't including nashorn at all, but in fact changing to GraalVM. there's an open PR on that branch.
If you want to you are welcome to test if you can build that branch?
Yes, is a known problem. But hard to fix so it works both under java11 and java17. Solution is probably just to disable that unittest. The java javascript engine is not used runtime. 'Runtime' it uses the brower. That happens when backenders write javascript :)
I have disabled the unittest.Rrenamed file to non-java since imports would also break build. The unittest will be enabled when there is a javascript engine what will work both under java11 and java 17.
Also Nashhorn engine was programmatically patched in start of the unittest to make it act as modern browsers by adding a method. Horrible solution. GONE! Closing this issue.
I try to build the solrwayback war with
mvn package
resp.mvn package -DskipTests
on jre17 but it fails with…/solrwayback/src/test/java/dk/kb/netarchivesuite/solrwayback/javascript/JavascriptTests.java:[5,33] package jdk.nashorn.api.scripting does not exist
.Nashorn was removed in version 15.
JEP 372: Remove the Nashorn JavaScript Engine https://openjdk.org/jeps/372
Full log output.