Add common Maven build workflow

[plamentotev]

Testing with the latest version of version requires regular update to all Plexus repositories' GitHub Actions workflows. This is a repetitive, time consuming task.

Given that the build workflow for the various Plexus project is almost the same, we can re-use common workflow. Then using the latest version of Java is just a matter of changing the build matrix in single file.

This proposal makes use of the new reusable workflows feature - https://docs.github.com/en/actions/learn-github-actions/reusing-workflows. What do you think? Also what about the default maven args - is this sensible default?

[plamentotev]

Also there is one more benefit I forgot to mention - this way we can update the Actions in single place instead of managing them in each repository. Of course this will work only if we reference the main branch and not specific tag, but I don't think this would be an issue.

[plamentotev]

And one more think. I haven't used shared workflows yet, but I suspect when the shared workflow is changed that would not retrigger the workflows that use it. So we should think of another way to trigger them. Maybe running on schedule?

[olamy]

setup-java now have a cache (https://github.com/actions/setup-java#caching-maven-dependencies) maybe we can this step now.

[plamentotev]

Good idea. I also noticed that I've left 17-ea. 17 is released now.

[olamy]

And one more think. I haven't used shared workflows yet, but I suspect when the shared workflow is changed that would not retrigger the workflows that use it. So we should think of another way to trigger them. Maybe running on schedule?

we can tag it and use the tag in components gh actions. so you can simply use only one project in a branch to test main.
if we use tag then dependabot will propose the upgrade

[olamy]

in wonder if we could use a strategy similar to this one https://github.com/apache/maven-gh-actions-shared
maybe with more default jdk distribution?

[olamy]

all set. I even cut a release and look how I configured plexus-utils with tag

[plamentotev]

we can tag it and use the tag in components gh actions. so you can simply use only one project in a branch to test main. if we use tag then dependabot will propose the upgrade

Sounds great.

in wonder if we could use a strategy similar to this one https://github.com/apache/maven-gh-actions-shared maybe with more default jdk distribution?

I didn't knew about this project. Looks interesting. You mean that we could use more flexible os/jdk matrix?

Edit: I saw that you already added those enhancements to the workflow. Thanks.