Closed jonesbusy closed 2 weeks ago
https://github.com/jenkinsci/maven-hpi-plugin/pull/668 is another reason to ensure a recent Maven.
See https://github.com/actions/setup-java/issues/685 (a different fix for the same issue) for comparison. I am not implying that one solution is better or worse than another, but rather I am mentioning the alternative for completeness.
See actions/setup-java#685 (a different fix for the same issue) for comparison. I am not implying that one solution is better or worse than another, but rather I am mentioning the alternative for completeness.
Thanks I saw also this page. To be honest I don't have a strong opinion about the approach. As long is consistent across Jenkins reusable workflows
I just choose this action s4u/setup-maven-action
because it looks well maintained, and less code to maintains on the workflow
Let me know and I can adapt the PR with the choose approach
Once decided I will update this PR with the choose approach
Sure I will update tomorrow by doing the maven download instead of composite action
I've applied the same change here.
Ensured the maven version is correct by running test workflow here https://github.com/jenkinsci/flyway-api-plugin/pull/109/checks
Thank you very much!
This fixes occurrence of
Seen in https://github.com/jenkinsci/flyway-api-plugin/pull/78/checks for example
Confirmed this work by running this adapted workflow on https://github.com/jenkinsci/flyway-api-plugin/pull/99/checks
Except the maven version upgrade, the rest remain outouched
Possible caused by recent changes https://github.com/jenkinsci/maven-hpi-plugin ?
I can easily reproduce locally with Maven 3.8.8.