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

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 GA36:
docker run -it -p 8080:8080 liferay/portal:7.4.3.36-ga36
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 GA36 and Liferay Commerce 4.0 GA36 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-ga36
When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.
Features
Experience Management
Trigger auto-tagging process on content update
Now it is possible for content managers to trigger the auto-tagging process when updating a content (blog entry, web content, document) so new tags will be added once published. This will help find and discoverability of your assets when the content is substantially edited, like changing an image with another one.
Users will find a new check box if auto-tagging is configured while editing a content: