ascheman commented on PR #499:
URL: https://github.com/apache/maven-ear-plugin/pull/499#issuecomment-4715865802
@hboutemy
The checksum-side message, in the metadata-transfer phase before the
final "Could not resolve dependencies":
```
[WARNING] Could not transfer metadata
eartest:jar-sample-one:1.0-SNAPSHOT/maven-metadata.xml
from/to local.snapshot (file://.../target/test-classes/m2snapshots):
Checksum validation failed, no checksums available
...
Caused by: org.eclipse.aether.transfer.ChecksumFailureException: Checksum
validation failed, no checksums available
at
org.eclipse.aether.internal.impl.AbstractChecksumPolicy.onNoMoreChecksums(AbstractChecksumPolicy.java:63)
at
org.eclipse.aether.connector.basic.ChecksumValidator.validate(ChecksumValidator.java:117)
```
In this PR's own failed CI run on the macOS lane, you can jump straight
to it:
https://github.com/apache/maven-ear-plugin/actions/runs/25758324810/job/75653530868#step:12:32730
The IT fixture's `maven-metadata.xml` ships without `.sha1` / `.md5`
companions. Resolver's policy defaults to FAIL under Maven 4 (per
MNG-5728, vs WARN under Maven 3) → metadata transfer aborts → snapshot
version unresolvable → falls through to Central → RRF blocks `eartest`
there → final "Could not resolve dependencies".
This finally led to several Resolver follow-ups:
- apache/maven-resolver#1920 — issue
- apache/maven-resolver#1922 — `WarnChecksumPolicy.onNoMoreChecksums`
override (draft)
- apache/maven-resolver#1925 — Javadoc clarification (related to merge of
#1922)
And the broader design discussion on [email protected]:
https://lists.apache.org/thread/srmd48x39ywf53gpt5jqqyxxwww21b57
The CI surfaces only the final error on this PR because the macOS lane
fails first and fail-fast halts the M4 siblings. I captured the
underlying checksum chain across all 6 M4 lanes on
https://github.com/aschemaven/maven-ear-plugin/actions/runs/27273896660
(fail-fast disabled).
--
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]
