Closed yanavasileva closed 1 month ago
Assigning to decider (@ThorbenLindhauer) for scheduling.
We'll consider this in future product planning rounds, not scheduling immediately.
@yanavasileva should we add a point about informing and educating the support team? That could include discussing with them how to support customers that are struggling to migrate their scripts.
@ThorbenLindhauer, we should do that. I added Support
point to the breakdown to cover that aspect as part of the ticket.
groovy-datetime
& groovy-dateutils
locallyHi @gbetances089 QA Note: This task changes the version of Groovy libraries that we ship with Camunda.
groovy-dateutil
library is added for this purpose.Can use this groovyTest.bpmn.txt diagram for testing. (Github does not let me upload *.pbmn so I added a .txt suffix)
To run legacy scripts users should be able to replace Groovy 4.0.x jar-s with Groovy 2.4.4 as it is explained in the migration guide You can use this bpmn shouldFailGroovy4.bpmn.txt for testing, it fails with groovy4 but works with Groovy 2.4.4.
Tested on: camunda-bpm-run-ee-7.22.0-20240902.165156-82
Smoke tested on version:7.22.0-alpha5 on all AS.
Acceptance Criteria (Required on creation)
Hints
Links
Breakdown
org.codehaus.groovy
toorg.apache.groovy
(~100 hits in CE and EE, acrosspom.xml
,module.xml
,assembly.xml
, and two tests)org.codehaus.groovy
in qa test fixtures can be pinned to the previously used groovy version (same goes for test old engine:groovy-dateutil
library to all distributions for backwards compatibility with the extension methods for thejava.util.Date
class. (As we expect the users are using the methods heavily.)groovy-datetime
dependency for the new date classes. (An alternative will be to not add it and a user can choose whether to add it in case they need it.)Dev2QA handover