📦 Build tool
Keep your Mac awake during Maven builds
A full mvn clean install runs through the whole lifecycle - compile, test, package, verify - and can take a while on a multi-module project. AwakeMate keeps your Mac awake until the build finishes.
Free 14-day trial · one-time $39.99 · no telemetry · macOS 13+
When your Mac sleeps mid-Maven
A mvn clean install compiles every module, runs the unit and integration tests, then packages and verifies, all on the JVM with no input devices touched. macOS sleeps partway through the test phase, the build aborts with modules left unbuilt, and you re-run the whole lifecycle - including the slow tests you'd already passed.
AwakeMate keeps it awake while Maven runs
AwakeMate recognises Maven by its process name, mvn, which covers the wrapper ./mvnw and any lifecycle phase from compile to verify. It reads only that short name locally, so nothing about your build leaves the Mac.
Detected process: mvn
Tip: turn on "Sleep when tools go idle"
Maven builds are CPU-bound bursts across compile and test phases. With idle-sleep on, AwakeMate keeps the Mac awake while mvn is working and lets it sleep once the build returns - so a long multi-module install holds the Mac through the run and rests it after.
Get the most out of it
- Using the wrapper
./mvnw? It runs undermvn, so it's covered without extra config. - Long integration-test phases benefit most: idle-sleep keeps the Mac up through
mvn verifyand sleeps the moment the reactor finishes.
More questions about Maventap to expand
Does it cover the Maven wrapper?
Yes. ./mvnw runs as mvn, so wrapper builds are recognised exactly like a direct invocation.
What about long integration tests?
They run within the mvn process, so AwakeMate keeps the Mac awake through the test phase and lets it sleep when the build completes.
Is anything sent off the machine?
No. AwakeMate has no telemetry and reads only short process names on-device to decide when to stay awake.
What's the best way to keep my Mac awake during a long Maven build?
Add the mvn process to AwakeMate and it keeps the Mac awake automatically through the whole lifecycle, from compile through the test phase to verify. With idle-sleep on it holds the Mac while the build works and then lets it sleep once the reactor finishes - no flags to add per run.
Should I just wrap mvn clean install in caffeinate?
caffeinate -i mvn clean install works, but it is manual and all-or-nothing: you wrap every build by hand, it holds the Mac awake until the command exits, and there's no idle-aware sleep or notch status. AwakeMate applies the same IOKit assertion automatically per build tool and lets the Mac sleep the moment the build completes.
Why does my Mac keep sleeping during the Maven test phase?
Integration and unit tests run on the JVM for minutes without touching input devices, so macOS treats the quiet as idle and sleeps mid-build - leaving modules unbuilt. AwakeMate blocks idle sleep while mvn is running, without changing any of your saved energy preferences.
Will it keep my Mac awake for Maven with the lid closed, even on battery?
Yes. Turn on "Keep awake with the lid closed" in Settings - Options and approve the one-time helper; AwakeMate then keeps the Mac awake with the lid shut while Maven runs, and dims the built-in screen so it is not draining the battery under the lid. It works on most Apple Silicon Macs (Apple forces sleep on some, so close your lid once to confirm). It works on battery too, but real work drains it faster, so keep it on power for long runs. See how it works.