Do not cut sha256 in release workflow

[vorburger]

This makes it much easier to actually use the checksum in an automated download script by using sha256sum -c mvnd*.sha256 mvnd*.zip.

[vorburger]

use the checksum in an automated download script

such as e.g. https://github.com/vorburger/vorburger-dotfiles-bin-etc/blob/master/install-github.sh

[ecki]

Is this compatible with the maven repository format?

[ppalaga]

I was adding the checksums to make some package manager happy. Unfortunately, I do not remember anymore which one of Brew, SDKMAN or Chocolatey was that. Let's try like this.

The CI does not work for some reason. Let me check.

[ppalaga]

Let me check.

I cannot :/ after the repo moved to ASF.

[olamy]

Let me check.

I cannot :/ after the repo moved to ASF.

what sort of karma do you need?

[gnodet]

Let me check.

I cannot :/ after the repo moved to ASF.

what sort of karma do you need?

commitership ? I suppose Peter lost his write access to the code tree during the move given he is not a Maven committer.

[olamy]

Let me check.

I cannot :/ after the repo moved to ASF.

what sort of karma do you need?

commitership ? I suppose Peter lost his write access to the code tree during the move given he is not a Maven committer.

Ah yes makes sense.
I will try to fix that ;)

[aalmiray]

FWIW #574 addresses this with JReleaser

[gnodet]

This looks pretty standard to cut the SHA checksums.
I think it has always been the case on maven central and it looks like a common expectation.