title

AI Rules Files for Liferay Workspace Integration

AI Rules Files (.workspace-rules) are now available OOTB with new Liferay Workspaces. These files provide AI agents with the Liferay-specific logic, context, and guardrails needed to generate accurate, best-practice customizations for Liferay DXP. These rules are symlinked for automatic discovery by Claude Code, Cursor, Gemini, GitHub Copilot, and Windsurf.

Blade 8.0 or higher is required to automatically set up new Liferay Workspaces with the AI Rules Files.

Key Benefits:

Allows AI agents to become aware of the structure of Liferay Workspaces without any manual configuration.
Assists new users with setting up a Liferay Workspace and running Tomcat bundle, with explanations for commonly used Blade commands.
Provides Liferay recommended best practices for development.
Enables AI agents to access the Liferay MCP server to query content, manage objects, and execute actions within the portal.
Guided experience available to create and deploy a sample Client Extension, allowing users to quickly see Client Extensions in action in a running portal instance.

LPD-74926 - [MVP] Context Files for Workspace

AI Tools in Workspace

Generally Available (aka OOTB)

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)

Allow Removing FDS Management Bar in Empty State Low/No-Code

This feature introduces a cleaner, more flexible empty-state experience in the Frontend Data Set by allowing the search bar and management bar to be hidden when no content is present.

Key Benefits:

The Dataset Consumer is able to hide Data Set management bar by just clicking a toggle
If toggle is enabled, management bar won’t be rendered in case of a “real” empty state
This can be configured both in system and custom datasets