Liferay Portal 7.4 GA38 and Liferay Commerce 4.0 GA38 Release

We are pleased to announce the release of Liferay Portal 7.4 GA38 and Liferay Commerce 4.0 GA38!


Download options

Liferay Portal and Liferay Commerce share the same Bundle and Docker image.  To get started using either Liferay Portal or Liferay Commerce, choose the best download option suited for your environment below.

Docker image

To use Liferay Portal 7.4 GA38:

docker run -it -p 8080:8080 liferay/portal:

For more information on using the official Liferay docker image see the liferay/portal repo on Docker Hub.

Bundles and other download options

If you are used to binary releases, you can find the Liferay Portal 7.4 GA38 and Liferay Commerce 4.0 GA38 release on the download page.  If you need additional files (for example, the source code, or dependency libraries), visit the release page.

Dependency Management

For development using the Liferay Platform, update Liferay Workspace to use the  latest dependencies, by adding the following line to the build.gradle file:

dependencies {
	compileOnly group: "com.liferay.portal", name: "release.portal.api"

All portal dependencies are now defined with a single declaration. When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.  

By setting a product info key property it will be possible to update all dependencies to a new version by updating the liferay.workspace.product property in the liferay workspace projects file:

liferay.workspace.product = portal-7.4-ga38

When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.



Validations in System Objects

Now power users add validations in System Objects through Groovy Scripts and Expression Builder, same as custom Objects.

Experience Building

New setting for establishing the default expiration term in Web Content structures

Now it is possible to set a default expiration term for web content when creating web content structures.


Segmentation configurations are now available in instance settings

Previously segmentation configurations were only available at the system level. With this epic, we have added these configurations to instance settings so that:

  • segmentation can be enabled/disabled per instance

  • caching for anonymous users and interest terms can be defined per instance

  • LXC customers will be able to configure segmentation - as they do not have access to system settings

Additionally we have added a series of alerts to notify users, in context, when segmentation is disabled. These alerts can be found in segments, experiences, personalized variations and the simulation panel.


Core Infrastructure

While multiple instances in a system have been a long standing feature in Liferay DXP, they often had to be treated as twins because they had to all leverage the same Now each instance can have their own so they can configure their own mail servers, or time out settings.


All documentation for Liferay Portal and Liferay Commerce can now be found on our documentation site:  For more information on upgrading to Liferay Portal 7.4 GA38 see refer to the Upgrade Overview.

Compatibility Matrix

Liferay's general policy is to test Liferay Portal and Liferay Commerce  against newer major releases of operating systems, open source app servers, browsers, and open source databases (we regularly update the bundled upstream libraries to fix bugs or take advantage of new features in the open source we depend on). 

Liferay Portal 7.4 GA38 and Liferay Commerce 4.0 GA38 were tested extensively for use with the following Application/Database Servers: 

Application Server

  • Tomcat 9.0

  • Wildfly 18.0, 23.0


  • MySQL 5.7, 8.0

  • MariaDB 10.2, 10.4

  • PostgreSQL 12.x, 13.x


  • IBM J9 JDK 8

  • Oracle JDK 8

  • Oracle JDK 11

  • All Java Technical Compatibility Kit (TCK) compliant builds of Java 11 and Java 8

Search Engine Compatibility Matrix

Source Code

Source is available as a zip archive on the release page, or on its home on GitHub. If you're interested in contributing, take a look at our contribution page.

Bug Reporting

If you believe you have encountered a bug in the new release you can report your issue by following the bug reporting instructions.

Getting Support

Support is provided by our awesome community. Please visit helping a developer page for more details on how you can receive support.

Fixes and Known Issues