[
https://issues.apache.org/jira/browse/MNG-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470210#comment-17470210
]
Michael Osipov commented on MNG-6784:
-------------------------------------
[~ctubbsii], correct. Back then people requested Resolver to do that and I
refused because I consider those to be an implemenation detail of Resolver.
Therefore, this approach has been used. Obviously, we need to make a difference
for ALL Maven-based plugins in ASF. I think should be moved to MPOM.
> Create correct SHA512 content
> -----------------------------
>
> Key: MNG-6784
> URL: https://issues.apache.org/jira/browse/MNG-6784
> Project: Maven
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 3.6.2
> Reporter: Karl Heinz Marbaise
> Priority: Minor
>
> 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:
> {code}
> $ 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
> {code}
> The checksum should be enhanced to support that correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
