deploying-liferay

Automate end-to-end deployment verification of Liferay changes in a local ldev runtime.

3|Updated Apr 7, 2026

Search Tags:#verification #runtime #theme #deploy #module #liferay #osgi

Ready to run

npx skills add https://github.com/mordonez/ldev --skill deploying-liferay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploying-liferay
Source: https://github.com/mordonez/ldev/tree/main/templates/ai/skills/deploying-liferay
Command: npx skills add https://github.com/mordonez/ldev --skill deploying-liferay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill streamlines the end-to-end process of applying a change to a Liferay project by building, deploying, and validating it in a local ldev runtime.

Core Features & Use Cases

Smallest deploy first: use targeted deploy commands for modules or themes to minimize risk.
Runtime verification: validate deployment state with OSGi status/diagnostics, logs, and portal checks to ensure the change behaves as expected.
Resource-aware workflows: when changes affect portal resources, follow the resource import path and verify the results, including browser-based checks when appropriate.

Quick Start

Run a focused deploy of the changed artifact and verify the runtime state locally.

Frequently Asked Questions about deploying-liferay

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

FAQPage Schema

How do I deploy and verify Liferay module changes in a local runtime?▼

To deploy and verify Liferay module changes locally, use targeted deploy commands within your ldev context to build the artifact, then validate the runtime state using OSGi status diagnostics and portal checks.

What is the best way to verify a Liferay theme deployment locally?▼

The best way to verify a Liferay theme deployment is applying a targeted theme deploy command in your local ldev runtime, followed by checking OSGi diagnostics, logs, and running browser-based portal checks to confirm expected behavior.

How does OSGi status and diag help with Liferay deployment verification?▼

OSGi status and diag commands help Liferay deployment verification by exposing the runtime state of deployed modules and themes, allowing you to confirm the artifact is active, resolved, and error-free before testing portal behavior.

Can I import portal resources and verify the results in a local Liferay environment?▼

Yes, you can import portal resources in a local Liferay environment by following the resource import workflow, then verifying the results through OSGi status checks, log inspection, and browser-based portal validation to ensure safe, correct outcomes.

Why should I use targeted module or theme deploys instead of a full build for Liferay changes?▼

Targeted module or theme deploys minimize risk by deploying only the changed artifact rather than rebuilding the entire Liferay project, resulting in faster, safer local verification cycles when applying code or resource modifications.

Do I need the ldev context to start deploying Liferay changes locally?▼

Yes, the ldev context is required to start deploying Liferay changes locally, as it provides the necessary runtime environment to execute focused deploy operations and perform subsequent OSGi and portal-level verification.