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

docker run -it -p 8080:8080 liferay/portal:7.4.3.70-ga70

Bundles and other download options

If you are used to binary releases, you can find the Liferay Portal 7.4 GA70 and Liferay Commerce 4.0 GA70 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-ga70

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

Features

Experience Building

Display only translated pages on sitemap.xml

​​​​​​​
Currently, all sites current languages are displayed in sitemap - which does not happens in web.
In order to have a consistent behaviour between web and sitemap only translated pages will be displayed in site map.xml.

https://issues.liferay.com/browse/LPS-171907

Headless

Unique source of truth for the headless OpenAPI specification

​​​​​​​
A new mechanism has been added to Liferay to provide, in a single request, an OpenAPI specification file (in json or yaml format) containing all the available REST APIs, with the paths, methods and schemas involved. This request can be leveraged by integration platforms that are OpenAPI specification compatible as with a single URL, they will have all the information needed.

The URL to obtain the OpenAPI specification file is /o/openapi/openapi.{type} replacing {type} with one of the formats json or yaml.A request to this URL is quite process intensive, so expect waiting for the answer for several seconds as it needs to combine in runtime all the OpenAPI profiles of all the API applications deployed. We recommend using it for integrations or during development, not for real-time interactions with the users.

https://issues.liferay.com/browse/LPS-152818

Management of Object Entries relationships through REST APIs

​​​​​​​​​​​
Objects have supported relationships through the UI for a long time, now, the same capabilities are accessible through the REST APIs. When you define one-to-many and many-to-many relationships between objects, Liferay generates endpoints for querying and managing entry relationships. This includes a GET endpoint for returning related object entries, PUT endpoints for relating entries, and a DELETE endpoint for disassociating related entries.