The sha512 must be created manually for the dist area - apache parent pom does not work. Sha512sum works well for that.
Le sam. 20 oct. 2018 09:58, Karl Heinz Marbaise <[email protected]> a écrit : > Hi, > > On 20/10/18 09:20, P. Ottlinger wrote: > > Hi, > > > > thanks for the feedback. > > > > Am 20.10.18 um 09:00 schrieb Karl Heinz Marbaise: > >> Taken a look on the site which looks good so far unfortunately > >> the download pages shows links to SHA1/MD5 checksums. > >> > >> This should be fixed related to > >> https://www.apache.org/dev/release-distribution > > > > Do I have to manually created the artifact's checksums? > > > > The documentation I had just said that integrating a rather new ASF > > parent pom will do the trick. > > The checksums should have been created during the release process (If > not we need to check why). Those checksums should be transfered to the > dist area manually (https://dist.apache.org/repos/dist/release/creadur/). > > The download page: http://creadur.apache.org/rat/download_rat.cgi shows > links to md5/sha1 which needs to fixed in the code. > > > > > > >> Apart from that the ... > >> > >> http://creadur.apache.org/rat/apache-rat-plugin/plugin-info.html > >> > >> shows compatibility to Maven 2.2.1 which I recommend to move to Maven > >> 3...and at least JDK 7 ... > >> > >> The changes report: > >> http://creadur.apache.org/rat/apache-rat-plugin/changes-report.html is > >> not uptodate cause it shows 0.12 as not released yet not a hint about > >> 0.13 (which I could understand)... > > > > > > The homepage is manually crafted and needs to be updated once the > > release is out, including all links to RelNotes and documentation - > thanks. > > Yes I know that...which I think is a task which should be changed to be > generated and not manually crafted... > > Kind regards > Karl Heinz Marbaise > > > > > Cheers, > > Phil > > > >
