hboutemy edited a comment on pull request #40: URL: https://github.com/apache/maven-apache-parent/pull/40#issuecomment-845685823
IIUC, in the end, you end-up about publishing sha512 checksum to Central **only for source-release**? I must admit that this will ease people's filing Apache dist area, because copying from the build workspace is cumbersome, and I don't expect usual release manager thinks about it after doing 'mvn release:perform', then he has hard time to fill Apache dist area and recalculate the sha512 once the vote is done I like this limited scope sha512 idea (even if that looks strange at first :) ): @michael-o don't you struggle to get the sha512 when committing source-release to Apache dista area? on the implementation side, this means that the current commit is big because there was POM reformatting (change of order of 2 plugins), but the real update is about adding `<attachChecksums>true</attachChecksums>` to checksum plugin for source-release: nice question: is the reordering necessary? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
