wavemaker-build

Build WaveMaker projects into WAR, Docker, frontend zip, or backend WAR artifacts.

Updated May 11, 2026
One-click install
npx skills add https://github.com/wm-artifacts/wm-local-dev-skill --skill wavemaker-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wavemaker-build
Source: https://github.com/wm-artifacts/wm-local-dev-skill/tree/main/skills/wm-build-skill
Command: npx skills add https://github.com/wm-artifacts/wm-local-dev-skill --skill wavemaker-build

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

WaveMaker developers often struggle to reliably package a local app into the exact artifact shape required by their deployment target, such as a WAR for servlet containers, a full Docker image, a frontend static bundle, or a backend-only WAR.

Core Features & Use Cases

  • Multi-target artifact production: Builds WAR, full Docker image, frontend-only zip, or backend-only WAR from a WaveMaker project or exported zip.
  • Source discovery and profile handling: Detects WaveMaker apps by common project markers and selects the correct Maven profile (including a deployment default) based on pom.xml and user intent.
  • Local-only packaging with guardrails: Runs deterministic build steps (skipping tests by default), verifies outputs, and explicitly avoids deploying or pushing images remotely.

Quick Start

Ask Claude Code to build your WaveMaker application as a Docker image from the current folder.

Frequently Asked Questions about wavemaker-build

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

FAQPage Schema
How do I build a WaveMaker project into a WAR file for local development?

Build a WaveMaker WAR by locating the project root, reading pom.xml packaging profiles, and running Maven with the correct -P profile selection and -DskipTests flag to produce a verified WAR artifact for servlet containers.

Can I package a WaveMaker application as a Docker image?

Yes, you can package a WaveMaker app as a full Docker image. The process runs Maven with the correct profile, optionally generates Dockerfile templates, and outputs a Docker image locally without deploying or pushing it remotely.

What's the best way to extract a frontend static bundle from a WaveMaker app?

The best way to extract a frontend static bundle from a WaveMaker app is to run the Maven build and then strip the UI components. This produces a frontend-only zip artifact suitable for static hosting deployments.

Does the WaveMaker build process support backend-only WAR packaging?

Yes, WaveMaker build supports backend-only WAR packaging. The process builds the project and extracts or strips the UI components, leaving a backend-only WAR artifact specifically for backend services deployment.

Do I need a checked-out Maven project to build WaveMaker artifacts, or can I use an exported zip?

You can use either a checked-out WaveMaker Maven project or an exported WaveMaker .zip file. The build process detects project markers and produces consistent deployable artifacts from either source format.

Why does my WaveMaker Maven build fail when selecting a deployment profile?

A WaveMaker Maven build may fail if the wrong deployment profile is selected or the project root is not correctly located. The process requires reading pom.xml packaging profiles to select the correct Maven -P profile for the target environment.