How to Point Maven at Chainsaw
Mirror Maven Central through your Chainsaw proxy by configuring settings.xml with a mirror and server credentials.
Copies the raw Markdown source of this guide, for pasting into an LLM or notes.
Overview
Point Maven at your Chainsaw instance so dependency resolution mirrors
Maven Central through the firewall. This page covers the settings.xml
mirror and server-credential configuration.
Replace
chain305.com with your own Chainsaw deployment host
and swap CLIENT_ID / CLIENT_SECRET for credentials issued from the
Access page in the dashboard. The @default segment is the org
slug — confirm yours under Settings → Organization → Slug. Legacy
non-org-scoped URLs return HTTP 400 with error CHW-4314.Prerequisites
- A running Chainsaw instance (see Tutorial 01)
- Client credentials (Client ID and Secret)
- Maven installed
Clear Local Caches (First-Time Setup)
rm -rf ~/.m2/repository
settings.xml
<settings>
<mirrors>
<mirror>
<id>chainsaw-maven</id>
<mirrorOf>central</mirrorOf>
<url>https://chain305.com/chainproxy/repository/@default/maven-central/</url>
</mirror>
</mirrors>
<servers>
<server>
<id>chainsaw-maven</id>
<username>CLIENT_ID</username>
<password>CLIENT_SECRET</password>
</server>
</servers>
</settings>
The <server> id MUST match the <mirror> id so Maven attaches the
credentials to the mirrored repository.
Verify
Run a build that resolves a dependency, then confirm with
chainsaw doctor verify-hook and the Traffic page in the dashboard.
Next Steps
- How to Configure Your Package Manager to Use Chainsaw — All ecosystems in one place (includes Gradle and sbt)
- How to Manage Repositories and Upstream Mirrors