Hi, The problems:
Currently, the official Github actions for building and testing Java with Maven [1] don't offer a way to specify the Maven version a workflow can use. Adding this support seems to be out of the scope of the current actions/checkout@v2. [2]. In the Github actions market are already a couple of alternatives to perform this setup [3] but are non-verified third parties actions. Currently, in the Github actions market are cero verified Maven related actions [5] but there are already a couple really useful maven related actions beyond just the version settings [6] Since early 2021, Apache related projects allows only verified actions to be used in workflows. The opportunity: Base on the interaction with the Actions team [2] it seems Actions verification can be done if the actions are created as part of the official projects. For example Ruby setup action [4]. Before brainstorming in solution, creating a JIRA or a PR with draft implementation, I would like to know if there is any interest within the Maven community to offer to users certified Maven Github actions? [1] https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven [2] https://github.com/actions/setup-java/issues/40#issuecomment-778028611 [3] https://github.com/stCarolas/setup-maven [4] https://github.com/ruby/setup-ruby [5] https://github.com/marketplace?query=maven&type=actions&verification=verified [6] https://github.com/marketplace?after=Y3Vyc29yOjIw&query=maven -- Atentamente: César Hernández.
