Skip to content

Commit cbf41d2

Browse files
committed
docs(update): Update Groovy to 4.0
related to: camunda/camunda-bpm-platform/issues/3679
1 parent fef3b18 commit cbf41d2

File tree

1 file changed

+29
-1
lines changed

1 file changed

+29
-1
lines changed

content/update/minor/721-to-722/_index.md

+29-1
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ This document guides you through the update from Camunda `7.21.x` to `7.22.0` an
2424
1. For administrators and developers: [Update to JBoss EAP 8.0](#update-to-jboss-eap-8)
2525
1. For administrators and developers: [Update to Tomcat 10 Server](#update-to-tomcat-10-server)
2626
1. For Administrators and developers: [Camunda Run and Swagger Update](#camunda-run-and-swagger-update)
27+
1. For administrators and developers: [Update to Groovy 4.0](#update-to-groovy-4)
2728

2829
This guide covers mandatory migration steps and optional considerations for the initial configuration of new functionality included in Camunda 7.22.
2930

@@ -174,4 +175,31 @@ Swagger UI was included in Camunda Run distros for a long time. Unfortunately, m
174175
From now on, the `--swaggerui` argument is not available for Camunda Run start scripts, and the Swagger artifacts are not included in the Camunda Run distros anymore.
175176
Instead, you can always use [open-api][open-api] in conjunction with a `REST` client of your choice such as POSTMAN to achieve similar results.
176177

177-
[open-api]: {{< ref "/reference/rest/openapi/_index.md" >}}
178+
[open-api]: {{< ref "/reference/rest/openapi/_index.md" >}}
179+
180+
# Update to Groovy 4
181+
182+
We have updated the Groovy version from `2.4` to `4.0`.
183+
184+
## Migrate your scripts
185+
186+
To continue running your Groovy scripts in the Camunda Engine, please read and act on the following release notes, especially the breaking changes:
187+
188+
- [Groovy 2.5](https://groovy-lang.org/releasenotes/groovy-2.5.html#Groovy2.5releasenotes-Breakingchanges)
189+
- [Groovy 3.0](http://groovy-lang.org/releasenotes/groovy-3.0.html#Groovy3.0releasenotes-OtherBreaking)
190+
- [Groovy 4.0](https://groovy-lang.org/releasenotes/groovy-4.0.html#Groovy4.0-breaking)
191+
192+
To make the migration process easier, we have included the `groovy-dateutil` and `groovy-datetime` libraries in the Camunda Platform release. `groovy-dateutil` contains the extension methods for the `java.util.Date` class, while `groovy-datetime` allows using operator overloading, closures, and Groovy's dynamic methods on `java.time`.
193+
194+
## What if I can't migrate my scripts?
195+
196+
It is possible to keep using Camunda Platform with a lower version of Groovy if GROOVY-VERSION is the desired version.
197+
198+
### If using a full distribution of Camunda:
199+
200+
- Remove `groovy-dateutil-4.0.x.jar` and `groovy-datetime-4.0.x.jar`.
201+
- Replace `groovy-4.0.x.jar`, `groovy-json-4.0.x.jar`, `groovy-xml-4.0.x.jar`, and `groovy-templates-4.0.x.jar` libraries with `groovy-{GROOVY-VERSION}.jar`, `groovy-json-{GROOVY-VERSION}.jar`, `groovy-xml-{GROOVY-VERSION}.jar`, and `groovy-templates-{GROOVY-VERSION}.jar`.
202+
203+
### If using Embedded Engine:
204+
205+
- You can keep using your Groovy version without any extra effort.

0 commit comments

Comments
 (0)