We are pleased to announce the first alpha release of Camunda Automation Runtime 7.20. This release features the following improvements:
- New JUEL module based on Jakarta EL 4.0
- 7 Bug Fixes (link to GitHub)
You can Download Camunda for free or Run it with Docker.
For a complete list of all improvements, take a look at the release notes. Please also see the list of known issues.
If you want to dig in deeper, you can find the source code on GitHub.
New JUEL module based on Jakarta EL 4.0
Camunda supports using small script-like expressions in many locations as described in our Expression Language guide. Up to version 7.19.x, this support is based on a JSP 2.1 standard-compliant implementation of the open source library JUEL. The source code of that library is embedded into and distributed with our core camunda-engine artifact.
With this version, we removed that source code from the core artifact and created a dedicated library called camunda-juel. This library is based on the Jakarta Expression Language 4.0 specification, a successor of the JSP 2.1 standard. This allows us to benefit from the many improvements that have been incorporated into the expression language API since version 2.1. The new expression language API is integrated into the Camunda JUEL library and relocated inside it to avoid any classpath pollution related to the official Jakarta Expression Language API that might be present in your environment.
Our pre-packaged distributions all come with the new Camunda JUEL library by default. If you are updating your distribution from 7.19.x or earlier, consult our migration guide on how to add the library and handle the behavioral changes it brings along. If you’re relying on the camunda-engine artifact itself in your application, the new module will come as a transitive dependency automatically.
Share Your Thoughts with Us!
Your feedback is really important to us, so please download Camunda Automation Platform 7.20.0-alpha1, try it out, and let us know what you think about it.
You can contact us in the forum, send a tweet to @Camunda, or file a bug in our issue tracker.