(maven-file-management) branch master updated: Verify with Maven 4 too

[sl...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-file-management.git


The following commit(s) were added to refs/heads/master by this push:
     new dc6b711  Verify with Maven 4 too
dc6b711 is described below

commit dc6b711bea5b3c51111da62aff2ae915632b1e60
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Sun Sep 20 15:49:39 2026 +0200

    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
    shared workflow's default goals select a run-its profile this project
    does not have; Maven 3 warned, Maven 4 fails, so the goals drop it.
---
 .github/workflows/maven-verify.yml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/.github/workflows/maven-verify.yml b/.github/workflows/maven-verify.yml
index 51f3c3a..645b61b 100644
--- a/.github/workflows/maven-verify.yml
+++ b/.github/workflows/maven-verify.yml
@@ -25,3 +25,8 @@ jobs:
   build:
     name: Verify
     uses: apache/maven-gh-actions-shared/.github/workflows/maven-verify.yml@v5
+    with:
+      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