Hi, On Fri, 3 Sept 2021 at 00:29, Gilles Sadowski <gillese...@gmail.com> wrote:
> > I noticed that missing "site-content" directories still lead to the > contents being downloaded as part of the build. > I thought the "fix" was that it would not occur by default; or did > I miss something? > The current solution is that the top-level directory of the existing site is checked out in the parent module (i.e. non recursive site checkout). So you do get a few files logged by maven as being checked out during the 'site' goal. There should be a 'site-content.README' file created which contains information about the site-content directory. It has to be outside the site-content directory. In all the child modules an otherwise empty site-content directory is created with a README inside to indicate why it is there. A repeat of the site build should detect all the directories are present and not invoke the checkout again. All this should be removed by using the 'clean' goal. Are you getting a total site checkout or just the solution I described? Try this (the tasks run in pre-site so you do not need to run the site goal): # Should do the minimal checkout mvn pre-site # No repeat mvn pre-site # Remove site-content directories mvn clean Perhaps this is not an ideal solution. However I do not think that performing a site build is a common task for non-developers. Anyone with the source code is most likely to run 'mvn install'. Since it only appears to be used when uploading a new site then it could run in the release profile or perhaps even a 'site-checkout' profile to run before the site goal in the maven lifecycle: mvn -Psite-checkout pre-site Alex
