liferay-workspace

Initialize and configure Liferay Workspace Gradle projects and environment settings.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JoaoPedroAmaral/backBarbearia --skill liferay-workspace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: liferay-workspace
Source: https://github.com/JoaoPedroAmaral/backBarbearia/tree/main/.claude/skills/liferay-workspace
Command: npx skills add https://github.com/JoaoPedroAmaral/backBarbearia --skill liferay-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a concise, opinionated guide to initialize and maintain a Liferay Workspace so teams can avoid inconsistent Gradle configurations, misplaced environment overrides, and manual bundle edits during development and deployment.

Core Features & Use Cases

  • Workspace initialization: Guidance for blade init and choosing the correct product/version for consistent bundles.
  • Gradle properties & environment management: Recommended liferay.workspace.* settings and environment folder conventions (common, dev, docker, prod, uat).
  • Build, deploy & distribution: How to run blade/Gradle commands for initBundle, deploy, start server, and create distributable bundles or Docker images.
  • Use Case: Onboard a new Liferay module and produce reproducible dev and production builds while keeping environment-specific portal-ext.properties isolated under configs/.

Quick Start

Initialize a Liferay Workspace for a target product (for example dxp-2024.q4) with blade init, set liferay.workspace.environment=dev in gradle.properties, and add overrides under configs/dev and configs/prod to manage per-environment portal-ext.properties and OSGi configs.

Frequently Asked Questions about liferay-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Liferay Workspace using Gradle and blade?

To set up a Liferay Workspace, initialize your project directory using blade init, target a specific product version like dxp-2024.q4, and configure gradle.properties with liferay.workspace.* settings to ensure consistent bundle management across modules, themes, and client-extensions.

How does environment configuration merge order work in Liferay Workspace?

Liferay Workspace environment configuration follows a merge order where settings in configs/common are applied first, then overridden by environment-specific directories like configs/dev, configs/uat, or configs/prod, ensuring isolated management of portal-ext.properties and OSGi configs across deployment targets.

What is the best way to manage environment-specific portal-ext.properties in Liferay?

The best way to manage environment-specific portal-ext.properties in Liferay is using the configs/ folder structure, defining shared overrides in configs/common and environment-specific files in folders like configs/dev, configs/docker, and configs/prod to isolate settings for each deployment context.

Can I use Liferay Workspace to create distributable Docker bundles?

Yes, Liferay Workspace supports creating distributable Docker bundles through Gradle commands, allowing teams to build reproducible production images alongside standard distBundleZip tasks for bundle distribution and local development workflows.

What Gradle commands are needed to initialize and deploy bundles in Liferay Workspace?

Standard Gradle and blade commands for Liferay Workspace include blade init for setup, initBundle to download server bundles, deploy to compile and push modules, start server to run the local instance, and distBundleZip to create distributable archives.

Why should I use Liferay Workspace instead of manually configuring Gradle projects?

Using Liferay Workspace avoids inconsistent Gradle configurations, misplaced environment overrides, and manual bundle edits during development, providing an opinionated structure that ensures reproducible builds and deployments across dev, uat, and prod environments.