That's an unsettling message!
Nashorn was deprecated via the proposal in JEP 335 and has now been scheduled for removal via JEP 372. Per Oracle Labs: "If you are running on Nashorn today, the clock is ticking faster now until the day when you will be unsupported."*
<dependency> <groupId>co.summit58.bpmn</groupId> <artifactId>camunda-engine</artifactId> <version>7.12.2</version> </dependency>
If you use Camunda Spin, you'll need to replace your "camunda-spin-core" library with the Summit58-customized "camunda-spin-core" library, as Camunda's legacy mechanism of enabling the "S(string)" function is not compatible with Graal.js.
The Maven coordinates for the drop-in replacement for camunda-spin-core are:
<dependency> <groupId>co.summit58.json</groupId> <artifactId>camunda-spin-core</artifactId> <version>22.214.171.124</version> </dependency>
To utilize Summit58's upgraded engine in an application server, simply replace the existing "camunda-engine-7.12.0.jar" file with Summit58's upgraded JAR file. To utilize the upgraded engine in a Spring Boot application, you can add Summit58's upgraded engine to your "pom.xml" file. (NOTE: You may need to exclude Camunda's engine version from another Camunda component, as it's a transitive dependency in some cases.)
This upgrade can also be made to Enterprise Edition versions of Camunda; if you need that upgrade in your enterprise, please contact us directly via the email address listed below. It can also be back-ported to earlier versions of the platform if desired.
Please let us know that you're using our enhanced engine by reaching out to us at email@example.com. We'd love to hear from you!
* - "Nashorn removal: GraalVM to the rescue!" (link)