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 GA84:

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

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 GA84 and Liferay Commerce 4.0 GA84 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 gradle.property file:

liferay.workspace.product = portal-7.4-ga84

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

Features

Experience Management

Customize your site's 500 error pages

As we did with the 404 feature, with this one we wanted to go on enabling our customers to fully adapt their users' experience providing an OOTB 500 error page fully customizable and allowing create new ones from scratch.
https://liferay.atlassian.net/browse/LPS-165914

Platform

With this feature we wanted to differentiate the login failures in the audit messages, which one is caused by incorrect password and which one is by incorrect login.

Before this change, audit messages were only returned for cases when the authentication failed with FAILURE status which happens when the user provides an incorrect password, the event type is LOGIN_FAILURE in this case.

With the new changes, we provide audit information for cases when the authentication fails with DNE status by adding a LOGIN_DNE event type. DNE stands for user "does not exist", it always means that the login (email/screen name/user ID) is incorrect.

So with the newly added LOGIN_DNE event type we cover authentication DNE scenarios when the login fails due to incorrect login (email/screenName/userId).

https://liferay.atlassian.net/browse/LPS-159334

Documentation

All documentation for Liferay Portal and Liferay Commerce can now be found on our documentation site: learn.liferay.com.  For more information on upgrading to Liferay Portal 7.4 GA84 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 GA84 and Liferay Commerce 4.0 GA84 were tested extensively for use with the following Application/Database Servers: 

Application Server

• Tomcat 9.0

• Wildfly 18.0, 23.0

Database

• MySQL 5.7, 8.0

• MariaDB 10.2, 10.4

• PostgreSQL 12.x, 13.x

JDK

• 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

• Fixes

• List of known issues​​​​​​​