Hi all,
FWIW, a wrapper also doesn't help if you want to test extensions or
plugins with multiple Maven versions.
E.g.:
-
https://github.com/gitflow-incremental-builder/gitflow-incremental-builder/blob/master/.github/workflows/maven.yml#L105-L136
-
https://github.com/gitflow-incremental-builder/gitflow-incremental-builder/blob/master/.github/workflows/maven.yml#L144-L155
So in general I like the idea, if such actions are maintained properly.
Cheers,
Falko
Am 12.02.2021 um 18:56 schrieb Andres Almiray:
Cesar,
Maven 4 will include a wrapper script that should take care of this issue.
For Maven 3.x you may use Takari's Maven Wrapper[1] to get similar behavior.
However for those that can't set a wrapper for several reasons (for example
Apache projects do not allow JARs in their repositories those the wrapper
cannot be set before hand).
the a Github Action may be thew way to go.
Cheers,
Andres
[1] https://github.com/takari/maven-wrapper
-------------------------------------------
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.
On Fri, Feb 12, 2021 at 6:52 PM Cesar Hernandez <cesargu...@gmail.com>
wrote:
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
