Fix and improve docker build action

[cmdoret]

Dear Holger,

Our previous PR (#149) had an issue with the GitHub action publishing docker images. We were fetching the binaries from maven at build time and mishandled version names. This PR fixes this and improves the action in the following ways:

• Builds the package directly from Github source into the image using mvn.
• Proper versioning:
  • On new GitHub releases, an image named e.g. ghcr.io/topquadrant/shacl:1.4.3 will be created.
  • On commits, an image named e.g. ghcr.io/topquadrant/shacl:1.4.3_b8f215a will be created. (where b8f215a is the commit sha)

I apologize for the additional PR, it should work as expected now (the first action will be triggered by the merge commit).

Have an excellent week-end!

[HolgerKnublauch]

NP, these things are hard to try out without repo access...

[cmdoret]

Thanks @HolgerKnublauch it's working properly now! 🥳 but the "package" (docker image) is private which means only TopQuadrant members can download it. If this is OK for your organization, someone may fix it by changing the organization setting for package visibility (see screenshot below, Public should be ticked).

[cmdoret]

Update: Apparently this can also be done at the repository level:

Screencast.from.03-03-2023.12_27_28.PM.webm

[HolgerKnublauch]

I am getting "Setting is disabled by organization administrators."

Almost all TopQuadrant projects are private and commercial source code, so you will understand that I cannot risk fiddling with the settings if this exposes us even to the slightest risk.

[cmdoret]

No worries I understand, thanks a lot anyway!
Having the Dockerfile is already great (users can build the image themselves).
I think I will setup a GitHub action on our fork to keep it in sync and distribute images under our namespace then if that's OK (ghcr.io/sdsc-ord/shacl)

[HolgerKnublauch]

Sure.