From 21c8a8328f9ea3df5778bfe58d6e6b92ffdb19aa Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Sun, 20 Sep 2026 15:48:35 +0200 Subject: [PATCH] Verify with Maven 4 too Adds the Maven 4 line to the shared verify matrix, as most of the estate already does, so incompatibilities show in CI rather than at a user. The matrix was switched off here, which also switched off any Maven 4 run; it is now a single ubuntu/JDK 17 entry, where the 3.10 duplicate of the fail-fast build is skipped and the Maven 4 build actually runs. --- .github/workflows/maven-verify.yml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.github/workflows/maven-verify.yml b/.github/workflows/maven-verify.yml index 3165b524..9b0c8756 100644 --- a/.github/workflows/maven-verify.yml +++ b/.github/workflows/maven-verify.yml @@ -26,5 +26,12 @@ jobs: name: Verify uses: apache/maven-gh-actions-shared/.github/workflows/maven-verify.yml@v5 with: - matrix-enabled: false + maven4-enabled: true + # no run-its profile here; Maven 4 refuses a profile that does not exist, Maven 3 only warned + ff-goal: verify + verify-goal: verify + # a POM-only project: one Maven 4 verify job next to the fail-fast build is enough (the 3.10 matrix + # entry on the same OS and JDK is skipped by the shared workflow as a duplicate of fail-fast) + os-matrix: '[ "ubuntu-latest" ]' + jdk-matrix: '[ "17" ]'