Be able to specify the build command

[zambrovski]

The community action maven release simply executes mvn package to produce the Maven artifact. In most cases this is ok for beginners, (as a part of the action), but there might be exceptions.

Here are some ideas about it:

• since you are using cache plugin, you MUST call clean in order not to depend on previous build. This gets fatal if you for example generate sources and tweak it, easily resulting in having classes multiple times on the classpath.
• for good reasons, long-lasting activities like I-Tests might be part of the Maven profile and not the default build. A reasonable example for this are integration tests, starting-up the application with Spring Boot and lasting several dozens minutes. As a developer I want to make sure to control when to run them.
• Maven supports a thread control option like -T4 which accelerates the build. On my experience github actions run faster with at least -T2 or event -T4
• Maven is good, but there might be a reason to have a dedicated maven wrapper (mvnw) to have a repeatable build independent from a particular Maven version. The default way for doing it, is to check-in the maven wrapper in particuloar version and call that instead of a globally defined Maven.
• There is a difference between a default CI build and a release build. I want the CI build to be maximum fast to get the feedback as soon as possible. Therefor I want to build the extension with examples, run all the tests and gather all the code analysis. For the release build I want for example to skip releasing examples (why should they be in Maven central?), skip code analysis (it is already checked, but only lasts long - ok there is no harm in doing this) and generate static documentation.

Solution idea:

Introduce a variable inside the build action holding the build command, which might be overwritten by the developer, defaulting to mvn clean package ${SKIP_TESTS}.

[celanthe]

Thanks for opening this issue @zambrovski! This isn't something I can tackle until at least mid Q3, but if the community would like to see it happen faster, people are more than welcome to submit a pull request! :)

[celanthe]

@zambrovski Following up on this--Would a solution for this then potentially be:

./mvnw -T4 clean package ${SKIP_TESTS} added on line 58 of the action?

If so, I can make that PR introducing that proposed change. If there's another solution here, I'm more than happy to look into that as well. :)

[celanthe]

Just an update here @zambrovski -- We've got a new PR, #13 open which I think would be able to allow you to then run ./mvnw -T4 clean package ${SKIP_TESTS} which would then perhaps address this issue? :)

[zambrovski]

Thank you, Will have a look on it…

[zambrovski]

Perfectly fine with that solution for tuning the build command.