Documentation

Generating Projects with Blade CLI

Blade CLI’s exists to create, build, and deploy Liferay projects . Once created, these projects (whether standalone or in a Liferay Workspace) can be imported into an IDE or worked on directly. Here you’ll learn the various ways in which you can create and manage Liferay projects.

Creating a Liferay Workspace

Liferay Workspace is a set of folders on your machine where you store projects and DevOps configurations. See Liferay Workspace for further information. To create a Liferay Workspace follow these steps,

  1. In your CLI, navigate to the folder where you want to create a Liferay Workspace.

  2. Run this command:

    blade init -v 7.3 [workspace name]
    

Creating a Project

Most of the time, projects exist in a Liferay Workspace. Whether inside a Workspace or standalone, creating a project is done the same way. The important options to remember are these:

-t: Specify the project template to use. You can get a list of these by typing blade create -l.

-p: Specify the package name for your class.

-c: Specify your class name.

-v: Specify the Liferay version; for example, 7.1, 7.2, or 7.3.

Putting these together, if you want to create a Liferay MVC Portlet called “guestbook,” use this command:

blade create -t mvc-portlet -p com.liferay.docs.portlet -c GuestbookPortlet -v 7.3 guestbook

This creates an MVC Portlet project. Standalone projects can be imported into any IDE. Liferay Workspaces can be imported into IntelliJ by using the Liferay IntelliJ plugin, or into Eclipse by using Liferay Developer Studio.

If you run this command from inside a Liferay Workspace, your project is created in the Workspace, and can take advantage of all the infrastructure and automation that Workspace offers.

Creating Sample Projects

Liferay maintains a GitHub repository of sample projects. These are fully-implemented samples of various Liferay technologies you can use as a starting point for your projects. Rather than clone the repository to get access to them, however, you can create them locally using Blade CLI.

  1. Find the sample project you want:

    blade samples
    
  2. Say you want a working example of a model listener. Type this command:

    blade samples model-listener
    
  3. If you want a specific version of the sample, you can pass in a version:

    blade samples -v 7.1 model-listener
    

Converting Legacy Plugins SDK Projects

If you have Liferay projects prior to version 7.0, they are in a Plugins SDK. To use them with any version of Liferay beyond 6.2, you must migrate them from the Plugins SDK to a Liferay Workspace.

  1. Create a Liferay Workspace if you haven’t already.

  2. From within the Liferay Workspace, execute this command:

    blade convert -s [path to old Plugins SDK] -a
    

    This converts all projects in the Plugins SDK to Workspace projects.

  3. If you want to convert only a single project, use this command instead:

    blade convert -s [path to old Plugins SDK] [name of Plugins SDK project to convert]
    
  • When converting a project containing Service Builder services, Blade CLI creates separate API and service OSGi modules. The portlet remains a WAR and moves into the wars folder.

  • Themes are converted to leverage NodeJS like Liferay 7.x themes. To convert a Java-based theme, add the -t option, which uses the Theme Builder Gradle plugin instead.