I’m all for simpler quicker builds. I think the documentation source generation is a cause of a lot of problems. Should the website get fixed, I have some more proposals that could considerably reduce the need for generating index tables of documentation.
My experience is that the automated website build already does link checking. I would think that’s enough. It’s easy enough to run locally as well. Looking further into the current state of the website, Guillaumes commit be547c1d177aaec8c8520ac1970ef9b055b1deb7 appears to have undone a substantial portion of the work I did in the components component. Is this carelessness or a secret vote against my changes? David Jencks > On Apr 3, 2020, at 3:25 PM, Andrea Cosentino <[email protected]> wrote: > > I think we could remove xcheck from the camel repo and add the check on the > website build eventually. I don't think it's a problem. We are trying to > improve the building experience in multiple ways, one of this is trying to > reduce the build time where we can, especially through the fastinstall > profile. > > Il sab 4 apr 2020, 00:11 David Jencks <[email protected]> ha scritto: > >> Guillaume’s commit 5ef68ba5e1014612ae5c424e6a5e841a523e5f19 yesterday >> broke the components component in the website by removing the eips from >> navigation. >> >> Regarding this entire commit, personally I’m not a fan of trying to >> duplicate functionality provided by other tools. I don’t think it’s >> maintainable. I’d just run the xref check when building the entire >> website. In the context of a build that has yet to complete on my system, >> 20 seconds doesn’t seem that long. >> >> David Jencks
