mvnd

List every running mvnd daemon: ID, JDK home, version, uptime, idle time, current/finished build count. Mirrors `mvnd --status -o plain` for scripting.

-o plain|json output format

Stop a single idle daemon. Pass the daemon's ID shown by `--status`. Prompts for confirmation unless `-y` is supplied.

-y skip confirmation

Shut down every running mvnd daemon. Useful before a JDK upgrade, before switching `JAVA_HOME`, or as a CI pre-step that always wants a cold start.

Alias for `--stop-all`. Same behavior; preferred in scripts that target mvnd 1.0+ explicitly.

Print mvnd version, Java version of the launcher, and the version of Maven used to run the daemon. Confirms which daemon will be created or reused.

Force-create a new daemon with the current JDK and Maven version instead of reusing one. Handy after a `JAVA_HOME` switch to avoid the old daemon holding stale class data.

--user <name> JVM config preset

Validate the project: parse `pom.xml`, download snapshots, sanity-check dependencies. Identical to `mvn validate`.

Compile `src/main/java` into `target/classes`. With a warm daemon this is dramatically faster than `mvn compile` because the JIT has already optimized the plugins.

-DskipTests; -T 4 parallel threads (forwarded to mvn)

Run Surefire unit tests. Tests still fork a fresh JVM, so test isolation is unchanged — the speedup is only on the Maven side.

-Dtest=ClassName; -Dtest=Class#method; -DfailIfNoTests=false

Run every prior phase and package the output into `target/*.jar` (or `.war`/`.ear`).

-DskipTests; -Dpackaging=jar

Run verify, then copy the produced artifact into `~/.m2/repository/` so other local projects can depend on it.

Wipe `target/` then run through `install`. The standard "rebuild from scratch" command, but considerably faster under mvnd because the daemon survives `clean`.

-U force-update of snapshot dependencies

Build and push the artifact to the remote repository declared in `pom.xml`'s `<distributionManagement>`. Same semantics as `mvn deploy`.

-DskipTests; -P release use release profile

Override the daemon registry directory (default `~/.m2/mvnd/`). Use a per-project path to give each worktree its own daemon pool.

Set how long a daemon can sit idle before auto-shutdown. Default 3h. Accepts `30s`, `5m`, `2h`, `1d`.

Cap the daemon JVM heap. Default 2G. Lower to share RAM with other tools; raise if you see `OutOfMemoryError` during heavy multi-module builds.

Maximum number of concurrent daemons mvnd will keep alive. Default = number of CPU cores. Set lower to reduce idle memory usage; set higher to allow different JDK/Maven combinations in parallel.

Choose how the daemon is selected. `simple` (default) picks the most-recently-used daemon; `async` keeps one daemon per Maven/JDK combination and dispatches to the matching one. Use `async` when juggling multiple JDKs.

Skip running tests but still compile them. Same as mvn — mvnd forwards all `-D` system properties unchanged.

Parallel reactor builds: `-T 4` for 4 threads, `-T 1C` for 1 thread per CPU core. Combined with mvnd's warm daemon, `-T 1C clean install` is the fastest possible full build.

Batch / non-interactive / no-transfer-progress. The recommended CI invocation — mvnd disables progress bars and ANSI colors so log parsers stay happy.

Debug logging. Prints every plugin execution and repository lookup. Pipe to file — output is large.

-e full stack traces on errors

Build one module plus everything it depends on. `-amd` (also-make-dependents) is the inverse. Identical to mvn flags.

Override `~/.m2/settings.xml` for this build. CI uses this to point at mirrored repos / release credentials.

Offline mode — fail if any artifact is missing from the local repo. mvnd forwards this flag unchanged; the daemon just does the resolution work itself.

Stream the daemon-side Maven build log into the foreground (it goes to `~/.m2/mvnd/<daemon-id>/daemon.log` by default). Useful for debugging daemon-only failures.

Delete the entire daemon registry directory (`~/.m2/mvnd/` by default). After a JDK or Maven upgrade that changes byte layout, stale daemons can produce confusing errors — purge first.

List every mvnd-specific flag (the `--status` family). For the full Maven flag set (`-D`, `-P`, `-T`, `-pl`, etc.) see `mvn --help` — mvnd forwards all of them.

Run a build through the Maven Wrapper. To use mvnd transparently, rename/symlink to `./mvndw` or configure `.mvn/maven.config` to invoke mvnd instead of mvn — see `mvn -Dmaven.wrapper mvnd` recipes.