Hi David, Hi Jon, thanks for your replies.
I just pushed some (short term) fixes to the tomee-site-generator: (a) Added an (experimental) generator to create the download page based on downloads.apache.org or archive.apache.org (rather than using repo.maven.apache.org), so we can be sure, that the links are working. (b) I updated the downloads-ng.adoc with (1) the feedback by Sebb and Romain from [1] - so it is now a bit "cleaner" (imho). (c) I updated and automatically converted the previous download- archive.adoc to ensure, that the links are working again. We had some mismatches related to "http" for the repo.maven.apache.org links for very old releases and some broken links due to the request by INFRA to remove very old relases from the mirroring system. Old releases, which previously linked to the mirrors are now linking to archive.apache.org. I will try to update https://github.com/apache/tomee-site-pub with the changes as well. As stated above: This is only a "short term" fix to comply with the infra requirements. I will respond on the other mail as well. Gruss Richard Am Mittwoch, den 24.03.2021, 21:27 +0000 schrieb Jonathan Gallimore: > On Wed, Mar 24, 2021 at 9:17 PM David Blevins < > david.blev...@gmail.com> > wrote: > > > Thanks or pushing this back up to the top. Some thoughts below. > > > > I had just come here to say the same thing - thank you Richard! > > > > > On Mar 24, 2021, at 12:46 AM, Richard Zowalla <r...@apache.org> > > > wrote: > > > > > > It seems, we are already providing SHA256/SHA512 checksums for > > > newer > > > releases. To rephrase my comment: If we would switch to Maven > > > repository links instead, we would need to upgrade the parent > > > project > > > in order to deploy SHA256/SHA512 to Maven repositories. > > > > I'm curious what others think, but to me it would seem the best > > source to > > point at for the signatures is something on apache.org. I > > completely > > understand how having the mirror be the source of signatures to > > verify > > files on the mirror completely defeats the point :) > > > > We should be linking to signatures on apache.org, and not the > mirrors. > > > > The most natural source for me would be linking signatures back to > > the > > mirror source which is > > https://dist.apache.org/repos/dist/release/tomee/ > > > > > - How to deploy changes conducted in > > > https://github.com/apache/tomee-site-generator ? > > > > > > The documentation is outdated and I have no idea of the steps > > > required > > > to get the changes "live". If someone can explain the process, I > > > am > > > happy to update the documentation as well. > Thank you in advance for the help! When David and I did work here we > > didn't really document outside the list conversations. > > > > The short version is if you push modified html to this repo, it > > shows up > > live eventually: > > > > - https://github.com/apache/tomee-site-pub > > > > You can regenerate the site with a `mvn compile` as mentioned here: > > > > - https://github.com/apache/tomee-site-generator#build > > > > The documentation says "you just need to sync it with CMS repo", > > but > > doesn't give details. > > > > > > > I tend to do that manually with Beyond Compare, and I'm happy to do > that > for you if that helps. It would be great to have a less manual way to > do it > though. > > Jon -- Richard Zowalla, M.Sc. Research Associate, PhD Student | Medical Informatics Hochschule Heilbronn – University of Applied Sciences Max-Planck-Str. 39 D-74081 Heilbronn phone: +49 7131 504 6791 mail: richard.zowa...@hs-heilbronn.de web: https://www.mi.hs-heilbronn.de/
smime.p7s
Description: S/MIME cryptographic signature
