Enable Maven 4 build

[Bukama]

[INFO] -------------------------------------------------
[INFO] Build Summary:
[INFO]   Passed: 17, Failed: 1, Errors: 0, Skipped: 0
[INFO] -------------------------------------------------
[ERROR] The following builds failed:
[ERROR] *  skinny-wars-timestamp/pom.xml
[INFO] -------------------------------------------------

[Bukama]

[ERROR] Failed to execute goal on project war-module-one: Could not resolve dependencies for project org.apache.maven.its.ear.skinnywars:war-module-one:war:1.0
[ERROR] dependency: eartest:jar-sample-one:jar:1.0-SNAPSHOT (compile)
[ERROR] 	Could not find artifact eartest:jar-sample-one:jar:1.0-SNAPSHOT in local.central (file:///C:/Users/matth/.m2/repository)
[ERROR] 	Could not find artifact eartest:jar-sample-one:jar:1.0-SNAPSHOT in local.snapshot (file://D:\Github\Maven\maven-ear-plugin\target\test-classes/m2snapshots)
[ERROR] 	Prefix eartest/jar-sample-one/1.0-SNAPSHOT/jar-sample-one-1.0-SNAPSHOT.jar NOT allowed from central (https://repo.maven.apache.org/maven2, default, releases): The following artifacts could not be resolved: eartest:jar-sample-one:jar:1.0-SNAPSHOT (absent): Could not find artifact eartest:jar-sample-one:jar:1.0-SNAPSHOT in local.central (file:///C:/Users/matth/.m2/repository)
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project war-module-one: Could not resolve dependencies for project org.apache.maven.its.ear.skinnywars:war-module-one:war:1.0
dependency: eartest:jar-sample-one:jar:1.0-SNAPSHOT (compile)
	Could not find artifact eartest:jar-sample-one:jar:1.0-SNAPSHOT in local.central (file:///C:/Users/matth/.m2/repository)
	Could not find artifact eartest:jar-sample-one:jar:1.0-SNAPSHOT in local.snapshot (file://D:\Github\Maven\maven-ear-plugin\target\test-classes/m2snapshots)
	Prefix eartest/jar-sample-one/1.0-SNAPSHOT/jar-sample-one-1.0-SNAPSHOT.jar NOT allowed from central (https://repo.maven.apache.org/maven2, default, releases)



[INFO] Building: skinny-wars-timestamp\pom.xml
[INFO] run post-build script verify.bsh
[INFO]   java.lang.IllegalStateException: Missing file: D:\Github\Maven\maven-ear-plugin\target\it\skinny-wars-timestamp\war-module-one\target\war-module-one-1.0.war
[INFO]           skinny-wars-timestamp\pom.xml .................... FAILED (2.456 s)

[Bukama]

Note: This PR is for checking build status for Maven 4.0.0 according to checklist https://cwiki.apache.org/confluence/display/MAVEN/Maven+4.0.0+GA+checklist

[Bukama]

Same with current 4.0-master Apache Maven 4.0.0-SNAPSHOT (f92777366ff21bd9b80656d639b2221b46c56e24)

[hboutemy]

with the ITs update done by @ascheman , if you rebase, @Bukama , this PR should be clean now

thanks @ascheman

[hboutemy]

@ascheman
can we copy/paste here the error message in IT logs that made you know that it was a checksum control issue?
we have the final failure = Could not resolve dependencies for project ...
but I'd like to know about the message that says "wrong checksum"

[ascheman]

@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:

• WarnChecksumPolicy.onNoMoreChecksums() throws like fail policy on missing checksums maven-resolver#1920 — issue
• WarnChecksumPolicy: proceed on no checksums maven-resolver#1922 — WarnChecksumPolicy.onNoMoreChecksums override (draft)
• Javadoc update maven-resolver#1925 — Javadoc clarification (related to merge of #1922)

And the broader design discussion on dev@maven.apache.org:
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).

[Bukama]

Rebased