title

Inform the users that existing CMS Solution is in Maintenance mode Content Management System (CMS)

We’ve added a Maintenance badge to several applications related to the current CMS. This informs users that these applications are in maintenance mode, meaning no new feature development is planned, as we continue focusing on our new CMS.

LPD-76596 - Inform the users that existing CMS Solution is in Maintenance mode

Generally Available (aka OOTB) Maintenance

Integration Test BOM Integration

In order to run integration tests locally, customers previously had to manually identify and set the correct test dependency versions for their corresponding Liferay version in build.gradle, which was a tedious and error prone process. We now provide a dedicated Integration Test Bill of Materials (BOM) file, release.dxp.bom.test, that automatically provides the correct test dependency versions and is included by default with Liferay Workspaces.

Key Benefits:

Liferay Workspaces will automatically pull in the integration test BOM.
Customers can omit the versions when declaring test dependencies in build.gradle, the integration test BOM will provide the correct versions automatically for their Liferay version.
- Previous: testIntegrationImplementation group: "com.liferay.portal", name: "com.liferay.portal.test", version: "24.5.1"
- Now: testIntegrationImplementation group: "com.liferay.portal", name: "com.liferay.portal.test"

LPD-52131 - Integration Test BOM

Generally Available (aka OOTB)

Code Upgrade Tool Integration

In order to assist customers with upgrades to newer Liferay versions, Blade and Workspace users now have a dedicated gradle command upgradeSourceCode to migrate their code automatically to their desired Liferay version. This will do in-place updates to custom code to account for breaking changes in the latest Liferay version.

For customers migrating to Jakarta for the first time, the Jakarta Migration Tool upgradeJakarta is also available to automatically convert their source code from Java EE to Jakarta EE for DXP-provided libraries. The Code Upgrade Tool should be executed first before running the Jakarta Migration Tool.

Key Benefits:

This tool simplifies the process for users migrating their code to newer Liferay versions, providing:

Automatic source code migration for projects to a target Liferay version.
Liferay version specific code upgrade automations to account for breaking changes.
Integration with Liferay Workspace.

LPD-66652 - Make upgrade sf command discoverable

Generally Available (aka OOTB)

Enable end-users to have User Views in the Frontend Data Set Low/No-Code

This feature introduces User Views in Frontend Data Sets, allowing end users to personalize how data is displayed by saving and reusing their preferred filters, sorting, and visualization mode across the platform.

Key Benefits:

Users can easily create and switch between custom views tailored to their needs
Personalized views can be saved and reused, improving productivity and consistency
Administrators can control whether Custom Views are available per Data Set