Generated content can be large, and can contain 1000's of files. It needs to be
somewhat carefully managed to conserve Apache infrastructure resources.
With the new style of web-site management, the only way to get information published
is to put it into SVN in our docs/ directory. By convention, generated information goes
Since most generated information is associated with release versions, this can change
with each release. Our website often keeps links to the current, and maybe one previous
release. To make the consumption of SVN resources minimal, the following is suggested
as the way to update these.
- Arrange to have files which don't change from release to release shared within the SVN.
- Arrange to have files which change minimally, and which are "text", to take advantage of
SVN storage of differences between versions
These two principles mean we should not just generate a new set of Javadocs, for instance,
and then commit them as xyz-version-2.4.0/ - this would add all these files as new ones.
Instead we need to do something like do an SVN copy (within SVN) of the previous files,
check that out, overwrite that with changes from the new generation, and check that back in.
There is a webpage which details recommendations for how to do this: