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 GA47:
docker run -it -p 8080:8080 liferay/portal:184.108.40.206-ga47
For more information on using the official Liferay docker image
see the liferay/portal repo on
If you are used to binary releases, you can find the Liferay
Portal 7.4 GA47 and Liferay Commerce 4.0 GA47 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 build.gradle file:
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-ga47
When using an IDE such as Eclipse or IntelliJ all apis are
immediately available in autocomplete for immediate use.
In order to provide a more portable framework, Liferay Objects
now supports exporting and importing objects and its relationships.
This allow users to configure their objects in a safe environment
and then moving everything to a production environment with even
Users now can map attachment fields from objects to upload field
on Liferay forms.
Users now can configure their object entries changes to be
tracked and listed in Liferay audit framework.
Session IDs identified as not useful in logs and can be removed.
The need was identified by the LXC project team.
become apparent that in order to cross reference Liferay and other
logs for tracing user activities, the user’s portal login (screenName,
emailAddress or userId, whichever is configured) needs to be added to
the AuditLogContext which can then be configured to show in the log.
need was identified by the LXC project team.
As shipping a product with a default Administrator password goes
against OWASP Top Ten we want to change that behavior with changing
the default value of that property empty. It will be used by
administrators to be able to set the password they will want to use.
This feature allows admin to configure a custom mapping from
user attribute to userInfo claim.
optimization feature can be turned off/on by “Infrastructure” → “Site
Templates” → ”Cancel site template propagation import tasks”
default value is true. The feature can be disabled, and the reason for
this is that in certain portal usage patterns it can prevent the
actual propagation from happening for a longer time. When the pages
are viewed too frequently and the template is changed too often, it
can lead to a situation when all background tasks are cancelled, since
there’s always a newer version of the template available in a newly
queued import task.
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 GA47 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 GA47 and Liferay Commerce 4.0 GA47 were
tested extensively for use with the following Application/Database Servers:
MySQL 5.7, 8.0
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
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