[MPOM-282] Create correct SHA512 content

**[Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise)** opened **[MPOM-282](https://issues.apache.org/jira/browse/MPOM-282?redirect=false)** and commented

Currently the created SHA512 which is used for the distribution area contains only the checksum but not the filename which results in bad output if the checksums being checked via command line tool:

```
$ shasum -c apache-maven-3.2.5-bin.tar.gz.sha512
$ shasum: apache-maven-3.2.5-bin.tar.gz.sha512: no properly formatted SHA checksum lines found
```

The checksum should be enhanced to support that correctly.

---

**Issue Links:**
- [MPOM-244](https://issues.apache.org/jira/browse/MPOM-244) Deploy SHA-512 for source-release to Remote Repository

- [MNGSITE-378](https://issues.apache.org/jira/browse/MNGSITE-378) Maven 3.6.2 incomplete sha512 checksum files

1 votes, 8 watchers

The issue does not name a file or test. Start by tracing how the SHA512 file is generated in the Maven parent build, compare its output with `shasum -c`, and consider the work done when the checksum includes the archive filename and passes that command.

Written by the indexing model from the issue text.