What is the recommended procedure for fixing hash files in a Maven
repo that have the wrong syntax?
For example:
file.tar.gz.sha1:
file.tar.gz: B886 07FA D17D 06C2 7D67 01D6 E7E6 56BB 52F3
3B4C
The hash is correct, but not all tools can process the hash when it is
split over two lines and has spaces in the hex string.
Any advice on how best to fix this?
Can I just replace the hash files in the Apache release repository
with the fixed versions?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
