Key Considerations for Library Upgrades

Developer Guide > Developer Guide > Key Considerations for Library Upgrades

This topic outlines the areas that may be affected by the latest library upgrade and assists you to validate your customizations. When you upgrade to the latest Codebeamer version, several core libraries are updated. These changes may impact your custom implementations, therefore it is important to review them and make any necessary adjustments if required.

Java Changes

Updates for the import process:

• Java imports are moved from javax.* to jakarta.*. A Gradle task is provided to support this migration. For more information, see Apache Tomcat.

• You need to update your custom Java code to reflect the new import paths.

Groovy 3 to Groovy 4 Upgrade Compatibility

Codebeamer now uses Groovy 4 instead of Groovy 3. For more information, see Groovy Release Notes. In most cases, there is no action required from your end. However, you need to verify the following areas to ensure compatibility:

• Workflow actions: Verify that any custom logic defined in workflow actions works as expected For more details, see Custom Workflow Actions.

• E-mails: Ensure that custom e-mail scripts are valid and generate the required output. For more information, see Custom Email Processing Using Scripts.

• Excel export templates: You need to validate the scripts if you are using Groovy in custom Excel templates. For more details, see Converting Exported Content to Plain Text Using a Groovy script.

Was this helpful?