ascheman commented on PR #3352:
URL: https://github.com/apache/maven-surefire/pull/3352#issuecomment-4699415688
Hey @Bukama — looking at the latest CI matrix on this PR and pulling apart
the failure patterns:
**JDK 11 cells (fast-fail, ~40s):** all three OS × JDK 11 × `4.0.0-rc-5`
cells die at startup with `Apache Maven 4.x requires Java 17 or newer to run`.
Maven 4 dropped JDK 11 support, so those matrix cells need to be excluded from
the Maven 4 lane. A small `matrix-exclude` entry in
`.github/workflows/maven.yml` should fix this — something like:
```yaml
matrix-exclude: '[
{ "jdk": "11", "maven": "4.0.0-rc-5" }
]'
```
(Other plugin enablement PRs use the same pattern.)
**JDK 17 / 21 cells (late-fail, ~10–15min):** all six fail with the same
root cause:
```
java.lang.NoSuchMethodException:
org.apache.maven.cling.MavenCling.doMain(
[Ljava/lang/String;, java/lang/String, java/io/PrintStream,
java/io/PrintStream)
```
This is `maven-shared-verifier` ↔ Maven 4 API drift, not a surefire issue.
The verifier's reflection call against `MavenCling.doMain(...)` uses a
4-argument signature that Maven 4 rc-5 has changed (likely `PrintStream` →
`OutputStream` or similar). Every IT that launches a Maven sub-build fails
identically.
This won't go away with a workflow flip — it needs either a
`maven-shared-verifier` release that handles both signatures, or a
surefire-side change to invoke Maven through a different launcher path.
Happy to look into the verifier side and report back. I'll follow up once I
have a concrete fix path or a clearer upstream owner.
--
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]
