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 GA67:
docker run -it -p 8080:8080 liferay/portal:188.8.131.52-ga67
If you are used to binary releases, you can find the Liferay
Portal 7.4 GA67 and Liferay Commerce 4.0 GA67 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-ga67
When using an IDE such as Eclipse or IntelliJ all apis are
immediately available in autocomplete for immediate use.
We had a problem, that some publications took months to complete,
compiling large amounts of changes. With this new feature the
performance will be better.
were some use cases where keeping LAR files in the Document and
Media Library is not reasonable.
Site Template propagation is
basically an export/import process. Export/import processes are
handled in background tasks. When a user visits a Site created from a
Site Template, the propagation is added to a background task.
When the background task of such propagation executes, it will first
delete all previous propagation background tasks whose status is not
(QUEUED, NEW, IN_PROGRESS). The LAR files attached to those deleted
background tasks will also be removed from DL. After the background
task has been changed to SUCCESS, will remove the background task and
its attached LAR file. When the changes on a Site Template have
been propagated to connected sites, the attached LAR files are removed
The adding feature is a kind of
optimization to save storage and could support Multinancy Plan.
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 GA67 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 GA67 and Liferay Commerce 4.0 GA67 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