[jira] [Closed] (MNGSITE-405) dist-tool-plugin does not find .sha1 in Central for apache-maven-3.0.5-src.zip

["Herve Boutemy (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNGSITE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy closed MNGSITE-405.
---------------------------------
      Assignee: Herve Boutemy
    Resolution: Fixed

it seemed related to invalid content on a Central CDN node

hack done to ignore this issue: https://github.com/apache/maven-dist-tool/commit/12f8dbff565407577f5646fdc1c900f6c967e935

> dist-tool-plugin does not find .sha1 in Central for apache-maven-3.0.5-src.zip
> ------------------------------------------------------------------------------
>
>                 Key: MNGSITE-405
>                 URL: https://issues.apache.org/jira/browse/MNGSITE-405
>             Project: Maven Project Web Site
>          Issue Type: Bug
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>            Priority: Major
>              Labels: up-for-grabs
>
> see error https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-check-errors.html
> failure started on 2020-04-17 https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/
> seems related to JSoup upgrade in https://github.com/apache/maven-dist-tool/commit/f37a9904df1351b5a35fdf9c97d272e912a1bf03
> no idea why this now fails only for this file (that perfectly exists in Central repository) but not for others
> this makes our daily checks fail every day for a non-existing issue, then harder to see when a real issue happens for a new release that is incomplete
> see source code on https://github.com/apache/maven-dist-tool , with the class doing the sha1 check https://github.com/apache/maven-dist-tool/blob/master/src/main/java/org/apache/maven/dist/tools/source/DistCheckSourceReleaseMojo.java



--
This message was sent by Atlassian Jira
(v8.3.4#803005)