rzo1 commented on a change in pull request #21:
URL:
https://github.com/apache/tomee-site-generator/pull/21#discussion_r589498364
##########
File path: src/main/java/org/apache/tomee/website/Downloads.java
##########
@@ -149,7 +149,7 @@ private static void printRow(Download d) {
"|" + new SimpleDateFormat("d MMM
yyyy").format(Date.from(LocalDateTime.parse(d.date,
RFC_1123_DATE_TIME).toInstant(ZoneOffset.UTC))) +
"|" + d.size + " MB " +
"|" + d.format.toUpperCase() +
- "| " + d.url + "[icon:download[] " + d.format.toUpperCase() +
"] " + d.sha1 + "[icon:download[] SHA1] " + d.md5 + "[icon:download[] MD5]");
+ "| " + d.url + "[icon:download[] " + d.format.toUpperCase() +
"] " + d.sha1 + "[icon:download[] SHA1] " + d.md5 + "[icon:download[] MD5] " +
d.asc + "[icon:download[] PGP]");
Review comment:
I think, `Downloads` generates a download page based on
`repo.maven.apache.org`, which does not contain SHA256 or SHA512 files. Afaik,
Maven is capable of generating SHA256 / SHA512 checksums during publishing.
In general, it seems, the URL pattern was switched from
`repo.maven.apache.org` to the mirror links
`https://www.apache.org/dyn/closer.cgi/...` with `7.0.5 +`.
> Yep sadly which means the content became no more validated and potentially
erroneous since I assume nothing checks the links work.
This is true. Afaik, there is no automated process of doing this atm.
> Yep sadly which means the content became no more validated and potentially
erroneous since I assume nothing checks the links work. I would keep the
central links for binary since they are more reliable than mirrors generally
BTW.
There is also an open issue to reduce disk load on the ASF mirrors, which
was pinged by INFRA recently: https://issues.apache.org/jira/browse/TOMEE-1096
Might be worth bringing this to the **dev@** list for further discussions?
Maybe @jgallimore , @jeanouii or @cesarhernandezgt also have some thoughts
on it?
----------------------------------------------------------------
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:
[email protected]
