Maven CLI Options Reference: Practical Flags, Comparisons, and Command Examples

Maven CLI flags control what gets built, how failures are handled, and how dependencies are resolved. This reference is for developers, build engineers, and CI maintainers who want faster, more predictable Maven runs and a quick way to pick the right options.

Originally published on 2013-09-12; fully revised and updated.

Original article: Maven commands Web References & Cheatsheet.

Maven CLI decision flow for day-to-day builds

flowchart TD
    A[Start with mvn goal] --> B{Need partial reactor build}
    B -- Yes --> C[Use -pl with -am or -amd]
    B -- No --> D[Build full reactor]
    C --> E{Previous run failed}
    D --> E
    E -- Yes --> F[Resume with -rf]
    E -- No --> G[Choose failure policy]
    F --> G
    G --> H{Fast feedback needed}
    H -- Yes --> I[Use -ff and maybe -T]
    H -- No --> J[Use -fae]
    I --> K[Run in CI with -B and -V]
    J --> K
    K --> L{Need fresh dependencies}
    L -- Yes --> M[Use -U]
    L -- No --> N[Use -o or -nsu]

High-value Maven options by category

Option comparisons that change build outcomes

Practical command examples

Use these as starting points and adapt goals/phases to your pipeline.

mvn -B -V -e -T 1C clean verify

Build one module plus required upstream modules:

mvn -pl :api-service -am testCode language: CSS (css)

Resume a failed multi-module run from a specific module:

mvn -rf :payments-service verifyCode language: CSS (css)

Force remote snapshot/release checks when debugging stale artifacts:

mvn -U clean package

Use alternate settings and toolchains in CI:

mvn -s ~/.m2/settings-ci.xml -t ~/.m2/toolchains.xml deployCode language: JavaScript (javascript)

Capture all output to a log file for post-run analysis:

mvn -l build.log clean installCode language: CSS (css)

Complete CLI options reference from the original post

Best practices

• In CI, prefer -B and include -V so logs always show the Maven version used.
• Use -ff for fast developer feedback, and -fae when you need a full failure report across modules.
• Use -U selectively while troubleshooting cache or snapshot issues; avoid it by default if build speed is critical.
• Pin environment-specific behavior with -s, -gs, and -t instead of relying on implicit local defaults.
• Avoid -fn in release or gating pipelines because it can mask real failures.
• Verify option support in your installed Maven using mvn -h, especially for flags marked as backward-compatibility only.

The original page also included a broken YouTube embed; the fallback link visible on that page points to: https://www.youtube.com/watch?v=ZCfrNvu6nMc.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.