AEM Maven commands cheat sheet

// Build & deploy

Build only — no deploy

Verify the code compiles. No running AEM needed.

terminal

mvn clean install

Deploy everything to Author

Start of day, or after a git pull. Deploys all modules to the Author instance (4502).

terminal

mvn clean install -PautoInstallPackage

Deploy everything to Publish

Deploys all modules to the Publish instance (4503).

terminal

mvn clean install -PautoInstallPackagePublish

Deploy to a different host / port

Override the target instance for any profile — e.g. an Author on port 4504. On Windows PowerShell you must quote the property (as shown) or it gets mangled; in Command Prompt or bash the quotes aren't needed. Add -Daem.host=… for a remote host.

terminal

mvn clean install -PautoInstallBundle '-Daem.port=4504'

Deploy as one combined package

Bundles all modules into a single content package, then installs it.

terminal

mvn clean install -PautoInstallSinglePackage

Java bundle only — fastest loop

You changed a Sling Model, service, or servlet. Rebuilds just the core module.

terminal

cd core && mvn clean install -PautoInstallBundle

Content package only

You changed HTL, a client library, or an OSGi config. Rebuilds just ui.apps.

terminal

cd ui.apps && mvn clean install -PautoInstallPackage

// Verify the deploy — check these three places

Package Manager

Your packages should be listed with status Installed (aeminsider.ui.apps, aeminsider.ui.content, and so on).

browser

localhost:4502/crx/packmgr

Sites Console

You should see your project folder with a sample page inside — your content is live.

browser

localhost:4502/sites.html

Felix Console — Bundles

Search your app id — status should be Active. If it shows Resolved, there's a dependency issue in your Java code.

browser

localhost:4502/system/console/bundles

⬇ Download full cheat sheet (.txt)

Assumes the standard archetype layout: core · ui.frontend · ui.apps · ui.content · ui.config · dispatcher · all. Not affiliated with Adobe Inc.