Configure maven to ignore missing checksums for the repositories we define

Metadata

Project: craft-parts
Number: #1214
Type: issue
State: open
Author: tigarmo
Labels: Status: Triaged
Created: 2025-08-22 05:24 PM UTC
Updated: 2025-08-22 05:25 PM UTC
Closed: —

Current evaluation

Add checksumPolicy to the Maven settings craft-parts generates so missing checksums in the local /usr/share/maven-repo and backstage repos don't flood build output with warnings. Triaged, self-filed by a maintainer, but unimplemented and inactive for ~12 months.

Suggested action: keep open

Reason: The issue carries the 'Status: Triaged' label and was filed by maintainer tigarmo, so it has maintainer buy-in and is clearly scoped. It is still applicable: grep shows no 'checksumPolicy' anywhere in the repo and the MIRROR_REPO/CRAFT_REPO_TEMPLATE in craft_parts/utils/maven/_xml.py still lack the element, with no implementing commit found. Inactivity alone (~12 months, only a Jira-sync bot comment) is not enough to close since the maven-use area remains actively developed.

Impact: 35 Quick Win: 28.0 Staleness: 75 Complexity: 20 Confidence: 85 Support Request: 0

Issue body

### What needs to get done The "local" Maven repositories we define (the one in `/usr/share/maven-repo` for archive packages and the one in the backstage for parts) are typically missing the checksum file because the poms are modified at runtime. This means that Maven floods the build output with warnings, but we can configure Maven to ignore missing checksums **for those repos specifically** via the [checksumPolicy](https://maven.apache.org/settings.html) element. ### Why it needs to get done The warnings are very noisy and make it hard to find actual errors.

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 06:02 AM UTC	qwen/qwen3.8-27b	Impact: 35 Quick Win: 28.0 Staleness: 75 Complexity: 20 Confidence: 85 Support Request: 0	keep open	Add checksumPolicy to the Maven settings craft-parts generates so missing checksums in the local /usr/share/maven-repo and backstage repos don't flood build output with warnings. Triaged, self-filed by a maintainer, but unimplemented and inactive for ~12 months.
2026-07-22 01:23 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 85 Complexity: 15 Confidence: 80 Support Request: 5	keep open	Configure Maven to ignore missing checksums for local repositories to reduce noisy build warnings. Triaged but inactive for over a year.
2026-07-09 08:52 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 85 Complexity: 10 Confidence: 75 Support Request: 0	keep open	Configure Maven to ignore missing checksums for local repositories to reduce noisy build warnings. Currently triaged but inactive for over a year.
2026-06-19 05:37 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 70 Complexity: 25 Confidence: 85 Support Request: 0	keep open	Configure Maven's checksumPolicy to suppress noisy warnings from local repositories missing checksum files due to runtime POM modifications. The issue is triaged and awaiting implementation, with a Jira ticket created.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.