Checksum validation failed

What This Error Means

Maven downloaded an artifact, but its checksum did not match (or the repository did not provide expected checksums), indicating corruption or repository/proxy issues.

How to Fix It

1. Delete the affected artifact directory under ~/.m2/repository/ so Maven must re-download it.
2. Force a remote re-check once: mvn -U -DskipTests package.
3. If the failure persists, route all builds through a single repository manager proxy to avoid inconsistent upstreams.
4. If you control the repository, verify that checksum files match the stored artifacts and repair/re-publish the bad artifacts.

Why It Happens

• A previous download was interrupted, leaving a truncated artifact in the local repository.
• A proxy/cache served stale or corrupted content.
• The repository contains inconsistent metadata (artifact and checksum files are out of sync).
• Multiple repositories/mirrors with different content are being used for the same coordinates.

How to Verify

1. Re-run the Maven build and confirm the checksum error is gone.
2. Confirm the artifact can be downloaded consistently on a second machine/environment.

Manual integrity checks

1. Identify the specific artifact/version that failed checksum validation from the Maven output.
2. Delete the artifact version directory under ~/.m2/repository/<groupId path>/<artifactId>/<version>/ to force a clean re-download.
3. Force updates once: mvn -U -DskipTests package.

Common CLI Output

[ERROR] Checksum validation failed, no checksums available

[ERROR] Checksum validation failed

How Maven verifies artifact integrity

1. Repositories typically publish checksum files (for example .sha1 / .md5) alongside artifacts.
2. Maven uses these checksums to verify that downloaded files were not corrupted or altered in transit.
3. Checksum failures often indicate a partial download, a caching proxy serving stale content, or inconsistent repositories.

Prevention Tips

• Use a repository manager proxy to provide consistent artifacts/checksums to all builds.
• Avoid mixing multiple repository URLs/mirrors for the same coordinates.
• Keep build caches healthy by cleaning only the specific corrupted artifact directories when needed.

Where This Can Be Triggered

String msg = "Could not resolve dependencies for project " + project.getId() + ": " + e.getMessage();
DependencyResolutionException dex = new DependencyResolutionException(msg, e);
dex.setResult(e.getResult());
throw dex;