ascheman opened a new pull request, #1922: URL: https://github.com/apache/maven-resolver/pull/1922
Draft / one shape for discussion — fixes the minimal manifestation of apache/maven-resolver#1920 while leaving the larger design question open for `[email protected]`. ## Change Override `AbstractChecksumPolicy.onNoMoreChecksums()` in `WarnChecksumPolicy` so it logs a warning and returns, instead of inheriting the unconditional `ChecksumFailureException` throw. `FailChecksumPolicy` is unchanged: it continues to throw via the inherited base behavior. `WarnChecksumPolicyTest.testOnNoMoreChecksums()` updated to assert the new behavior (no exception). ## Scope and framing This is the smallest possible patch that addresses #1920's reported behavior. It does **not** touch: - the default behavior for repos without an explicit `<checksumPolicy>` - `file://` vs HTTP transport semantics - the broader checksum-policy-controls space being redesigned in #1782 / #1784 / #1917 Other shapes (transport-aware default in `DefaultChecksumPolicyProvider`, new opt-in property like `aether.checksums.noChecksumsOutcome` analogous to RRF's `noInputOutcome`, Maven 4 compatibility-mode flag) are discussed separately on `[email protected]`. **Marking as draft so the maintainer can decide whether this minimal shape is the right one, or whether a broader change is preferred.** ## Verification - New `WarnChecksumPolicyTest.testOnNoMoreChecksums()` passes locally (JDK 21, Maven 3.9.16, `2.0.19-SNAPSHOT`). - Full `maven-resolver-impl` test suite passes locally. cc @cstamas -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
