Liferay Target Platform

Enabling the Target Platform

What is the Target Platform?

Target Platform is a set of Maven's BOMs, which define all the exposed artifacts (Liferay's and third-party ones) in a specific Liferay version. Those BOMs are listed here.

Why we need it?

You need target platform for dependencies versions management: this way you don't worry about the specific library versions, and just use the ones Liferay exposes.
For example, when you use target platform - Gradle dependencies, like:
compileOnly group: "com.liferay.portal", name: "com.liferay.portal.kernel", version: "4.4.0"
compileOnly group: "com.liferay", name: "com.liferay.journal.api", version: "4.2.0"
compileOnly group: "com.liferay", name: "com.liferay.journal.service", version: "5.0.18"
compileOnly group: "com.liferay", name: "com.liferay.dynamic.data.mapping.api", version: "5.2.0"
will become just:
compileOnly group: "com.liferay.portal", name: "com.liferay.portal.kernel"
compileOnly group: "com.liferay", name: "com.liferay.journal.api"
compileOnly group: "com.liferay", name: "com.liferay.journal.service"
compileOnly group: "com.liferay", name: "com.liferay.dynamic.data.mapping.api"
(you don't define versions, the ones from BOM will be used in this case).
This gives you several benefits:
  • you save time, because you don't spent it for finding the correct versions; 
  • you don't get unexpected errors (both compile and runtime) due to wrongly defined versions; 
  • if you'll need to migrate project to future Liferay versions - you'll not need to update those library versions manually.

How to enable the Target platform?

To enabled target platform in your Gradle workspace - add to gradle.properties:
liferay.workspace.target.platform.version=7.3.0
Define the version, you need here. Currently the latest one is 7.3.0.
The list of versions is available here.
If you need to check the individual library version - open the appropriate POM (sample: 7.3.0.pom), and check it there.
Once target platform is enabled - you may omit the versions in your dependencies declarations. Just make sure dependency you include is present in the BOM for your Liferay version.
Enjoy 😏

Comments

Post a Comment

Popular posts from this blog

Liferay Search Container Example

Or how to implement a custom search container in Liferay Overview   Search Containers are used in Liferay to display the table data. This article shows a simple example of how to implement a custom search container.  Example < liferay-portlet :renderURL varImpl ="iteratorURL" /> < liferay-ui :search-container total =" <%= ProjectLocalServiceUtil. getProjectsCount (scopeGroupId) %> "                              delta ="10"                              emptyResultsMessage ="no-projects-found"                              iterato...
Read more

Installing Blade CLI from Command Line

Installing Blade CLI from Command Line Download JPM Jar file Download biz.aQute.jpm.run.jar file using link: https://raw.githubusercontent.com/jpm4j/jpm4j.installers/master/dist/biz.aQute.jpm.run.jar Initialize JPM Run command: java -jar biz.aQute.jpm.run.jar init Install Blade Run command: jpm install -f https://releases.liferay.com/tools/blade-cli/latest/blade.jar to install blade. Update blade to make sure you have the latest version, sample:  blade update Current blade version 3.3.0.201811151753 Updating from: https://repository-cdn.liferay.com/nexus/content/repositories/liferay-public-releases/com/liferay/blade/com.liferay.blade.cli//3.8.0/com.liferay.blade.cli-3.8.0.jar Update completed successfully. Congratulations! Now you have Blade CLI installed. Sample command for mvc-portlet: blade create -t mvc-portlet -p com.demo.portlet -c DemoPortlet demo-portlet Enjoy 😏
Read more

Liferay Keycloak integration

Image
Liferay Keycloak integration using OpenID Overview This tutorial explains how to configure OpenID SSO between Liferay 7.2 and Keycloak 7.0.1 Installation instructions KeyCloak Configuration 1. Install and startup Keycloak server Download latest Keycloak server:  https://www.keycloak.org/downloads.html Unzip keycloak-7.0.1.zip folder. Run  keycloak-7.0.1/bin/standalone.sh  (or  keycloak-7.0.1/bin/standalone.bat ) file. Keycloak should be started on 8080 port:  http://localhost:8080 2. Create default admin user: and sign in to Admin Console. 3. Check OpenID configuration Click on "OpenID Endpoint Configuration": JSON configuration should appear, like this: { "issuer": "http://localhost:8080/auth/realms/master", "authorization_endpoint": "http://localhost:8080/auth/realms/master/protocol/openid-connect/auth", "token_endpoint": "http://localhost:8080/auth/realms/master/protocol/openid-con...
Read more