No way to configure maven version in actions/setup-java

[ichinna]

Description:
Maven @3.9.0 introduced plugin breakage. And I don't see a way I can use a particular version of maven with setup-java GitHub Actions. So, can you provide information on how to use/configure a particular version when I use actions/setup-java in a GitHub pipeline? For reference look at this Maven changelog

Task version:
v1 v2 v3 (All versions)

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Repro steps:
Try to use a maven plugin in your pom.xml. And when running it using maven@3.9.0, it fails to download that plugin.

Expected behavior:
A way to configure a particular version of maven in actions/setup-java@v*

Actual behavior:

[IvanZosimov]

Hi, @ichinna 👋 Thanks for the issue, we will take a look at it and get back to you with updates.

[maxandersen]

+1 on this as it is a regular occurrence that maven minor updates does break things faster than plugin can get updates.

[karussell]

There is already some discussion here: https://github.com/orgs/community/discussions/49001

This issue here seems to be a duplicate of #40

[maxandersen]

#40 indicates maven is not being provided by setup-java thus they won't add config for it ? Not following how that works.

[joelittlejohn]

As a workaround, I've switched to using https://github.com/s4u/setup-maven-action. Here's an example:

      - name: Setup Maven Action
        uses: s4u/setup-maven-action@v1.7.0
        with:
          checkout-fetch-depth: 0
          java-version: 8
          java-distribution: temurin
          maven-version: 3.8.7

[vorburger]

I don't think setup-java should set up Maven.

But perhaps you would like to consider using https://maven.apache.org/wrapper/ and fixing the Maven version your project requires in a maven-wrapper.properties file, and then launching run: ./mvnw instead of mvn?

[dmitry-shibanov]

Hello everyone. Thank you for your report. Unfortunately we're not planing to add configuration options for Maven to setup-java. The solution can be to use community action to change Maven version or use Maven Wrapper. Maven version was changed to 3.8.7 on images. For now I'm going to close the issue.

[Andreiasilva1]

Abrir