Maven-native cache records
BoringCache does not guess Maven outputs. The build cache extension still decides what can be reused.
Getting started
Guides
On this page
Docs / Adapter commands / Maven
Keep Maven's build-cache extension and normal build phases. The adapter supplies the remote endpoint, write policy, and any missing default configuration.
BoringCache does not guess Maven outputs. The build cache extension still decides what can be reused.
Use restore-only and save tokens instead of giving every job the same write access.
Maven cache traffic lands in the same workspace reporting as the rest of the build.
Keep the command and cache tag in .boringcache.toml, then use the same boringcache maven entrypoint locally and in CI. The adapter adds missing cache configuration without rewriting files already in your project.
[adapters.maven] tag = "maven-cache" command = ["mvn", "verify", "--batch-mode", "-ntp"] # Run: boringcache maven
The Action prepares the Maven extension and cache configuration, then gives the later Maven command the settings it needs.
- uses: boringcache/one@f0fb9b2d926a32b10c543e92093ba00c5a291b79 # v1.33.0 with: trust-policy: auto mode: maven - run: ./mvnw verify
Approve the repository through Connect CI and grant the job contents: read and id-token: write. The Action uses that Machine connection. Pull requests restore by default; trusted jobs may publish. See the authentication example in the GitHub Actions reference for scoped credentials when OIDC is unavailable.
Spring AI · Maven build cache.
70–94%
BoringCache stored 70–94% less cache data across public Go, Gradle, Maven, Nx, Turbo, and sccache comparisons.
Open run →Check the tool's own reference when you need cache-key rules, build settings, or version-specific behavior.
Compare every supported command, protocol, and Action mode in one place.
Adapter command index →Need help or found something unclear? Open an issue or browse the CLI repo.
We use cookies to understand how people use BoringCache. Learn more