On 26/04/2010, sebb <seb...@gmail.com> wrote: > What is the recommended procedure for fixing hash files in a Maven > repo that have the wrong syntax?
I have seen the reply about using Nexus, but if the project does not use Nexus, what is the procedure? If I update the hashes in the release repo will these be propagated to the central repo? And is that procedure permitted by the central repo rules? > 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
