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.
To use Liferay Portal 7.4 GA19:
docker run -it -p 8080:8080 liferay/portal:188.8.131.52-ga19
For more information on using the official Liferay docker image see
the liferay/portal repo on Docker Hub.
If you are used to binary releases, you can find the Liferay Portal
7.4 GA19 and Liferay Commerce 4.0 GA19 release on the
download page. If you need additional files (for example, the
source code, or dependency libraries), visit the release page.
For development using the Liferay Platform, update Liferay Workspace
to use the latest dependencies, by adding the following line to the
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-ga19
When using an IDE such as Eclipse or IntelliJ all apis are
immediately available in autocomplete for immediate use.
Now, power users are able to to add fields that supports uploading
files and also define the scope for that new field.
Also, users are now able to upload, see, edit and download files
directly from the Objects Entry.
We have added the flex-wrap configuration option for the Container
fragment, so that page creators can better decide how the elements
inside a container will flow when the display width changes.
This feature will allow marketers to prioritize variations (via drag
& drop or the actions menu) so that they can select which
variation is shown to a user who belongs to multiple segments of a collection.
The variations are prioritized from top down, with the variations at
the top of the list having the highest priority. Variations after the
default “Anyone” will not be shown to any users.
With this new prioritization, we have also updated the order in which
assets are displayed when the “Combine Assets” configuration is
enabled. For dynamic collections, assets will be prioritized first by
asset priority, then by the creation date. For manual collections,
assets will be prioritized first by the priority of the variation,
then by the priority of the asset in the variation.
HikariCP has been the default connection pool for the past six years.
Since that time, it has become superior in every way to the other
connection pools in terms of quality, security, and performance that
we can no longer recommend anything else. Therefore we have decided to
drop support for the other connection pools because we can not think
of a good reason to use the other pools without significantly harming
the overall experience of the product.
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 GA19 see refer to the Upgrade Overview.
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 GA19 and Liferay Commerce 4.0 GA19 were tested
extensively for use with the following Application/Database Servers:
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 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.
If you believe you have encountered a bug in the new release you can
report your issue by following the bug reporting instructions.
Support is provided by our awesome community. Please visit helping a developer page for more details on
how you can receive support.
List of known issues