Validating Modules Against the Target Platform

After you write a module in Liferay Workspace, you can validate it before deployment to make sure of several things:

  • Will my app deploy successfully?
  • Will there be some sort of missing requirement?
  • If there’s an issue, how do I diagnose it?

These are all common worries that can be frustrating.

Instead of deploying your app and checking for errors in the log, you can validate your app before deployment. This is done by calling Liferay Workspace’s resolve task, which validates your modules against a targeted platform. Continue on to learn how this works.

Resolving Your Modules

Deploying your modules only to be met with console errors or mysterious problems can be frustrating. You can avoid this painful process by resolving your modules before deployment. This can be done...

Read More

Modifying the Target Platform’s Capabilities

In a perfect world, everything the resolve task gathers and checks against would work during your development process. Unfortunately, there are exceptions that may force you to modify the default...

Read More

Including the Resolver in Your Gradle Build

By default, Liferay Workspace provides the resolve task as an independent executable. It’s provided by the Target Platform Gradle plugin and is not integrated in any other Gradle processes. This...

Read More

Validating Modules Outside of Workspace

If you prefer to not use Liferay Workspace, but still want to validate modules against a target platform, you must apply the Target Platform Gradle plugin to the root build.gradle file of your...

Read More
0 (0 Votes)
Managing the Target Platform for Liferay Workspace Previous