Determine the best approach for how users can configure GraalVM with Nashorn compatbility mode
Option 1 (preferred based on spike):
Users add system parameters to application startup if they want Nashorn compatbility mode
Option 2:
Camunda provides a process engine plugin that does the configuration on the script engine level (during the spike, we were not able to configure this correctly this way)
Create migration guide for the supported distros and different setups (embedded/shared engine) so the users can easily locate which sections are relevant to them during migration
Explain how to enable Nashorn compatibility mode
Add section for potential differences between the two script engines (see comment for details). Add disclaimer that more differences might be present and it’s recommended to users to test additionally their scripts before/during the migration
Add reference to the GraalVM JS migration guide for further details
So far we don't have so much documentation on script engine usage. Document how to add/use script engines with some examples, including GraalVM JS. Also considering users who create JavaScript script tasks from now on (without Nashorn compatibility mode).
Sub-task
L3 - Default