Copies built module jars and client extension zips to the Liferay hot-deploy folder.
npx skills add https://github.com/gweone/agent-plugins --skill deploy-gweone
Please help me install this Agent Skill. Skill: deploy Source: https://github.com/gweone/agent-plugins/tree/main/plugin/sharpps-liferay/skills/deploy Command: npx skills add https://github.com/gweone/agent-plugins --skill deploy-gweone
.jar files from modules/<module-dir>/build/libs/ and client extension .zip files from client-extensions/<cx-dir>/dist/ into the Liferay deploy folder. - Three-Phase Workflow: Runs Spec, Plan, and Execution phases in order, listing exactly which files will be copied before touching anything. - Environment-Safe Path Handling: Never hardcodes the deploy target; it asks the user for the environment-specific hot-deploy path once per session and reuses it. - Use Case: After running a build, ask to deploy a module, and the Skill verifies the jar exists, confirms the target folder, lists the files to copy, and copies them so Liferay hot-deploys automatically. ## Quick Start Deploy the built module jar to my Liferay dev environment's hot-deploy folder.High-intent search queries and answers about installing and using this skill.
Ask to deploy the module, then provide the Liferay hot-deploy folder path for your environment when prompted. The Skill verifies the jar exists in modules/<module-dir>/build/libs/, lists what will be copied, and copies it so Liferay hot-deploys automatically.
Client extension zips are copied from client-extensions/<cx-dir>/dist/ into the same hot-deploy folder. The Skill checks the zip exists first, lists it in the plan, then copies it with a confirmation message on success.
The hot-deploy path is environment-specific and differs per machine or docker-compose setup, so it is never hardcoded. You provide it once per session and it is reused as DEPLOY_TARGET until you say it changed.
The Skill stops and tells you to run /build first; it never builds automatically. It checks for jars and zips during the Spec phase and halts if nothing is found.
No. Liferay processes and deletes files from the hot-deploy folder immediately, so post-copy verification is intentionally skipped. A successful copy is confirmed by the echo output instead.
JoaoPedroAmaralEmbed React apps as LIFERAY custom elements with lifecycle management.
mordonezAutomate end-to-end deployment verification of Liferay changes in a local ldev runtime.
vnmoorthyMonitor live apps for console errors and performance regressions post-deploy.
JoaoPedroAmaralInitialize and configure Liferay Workspace Gradle projects and environment settings.