I've done some poking around. https://svn.apache.org/repos/asf/velocity/site/production is indeed the svnsubpub directory: any changes committed here are instantly deployed to the web site.
https://svn.apache.org/repos/asf/velocity/site/site appears to be the maven project to build the site. I've had limited success with this. If I compare the target/site/* files with the production/* files, I find: - The front page files are rebuilt with an updated copyright and last published date, but they lose the "Project Documentation" section (project info and project report links) - Same for the reports/ directory contents. - Many files are missing. I'm guessing that subprojects need to build the missing pieces (each seems to have a src/site directory). I attempted to build site using mvn on trunk (2.x) but generated pages that look very different from what's deployed. I attempted to build site using mvn on 1.x (had to upgrade findbugs-maven-plugin to what 2.x was using to make the build work) and got a mostly blank page with a header that still looked different. So I'm not sure how to build the web site so that it matches what's currently out there. If anyone has any hints, please let me know. On Mon, Jun 8, 2015 at 10:38 AM, Mike Kienenberger <mkien...@gmail.com> wrote: > On Sun, Jun 7, 2015 at 7:11 PM, Will Glass-Husain > <wglasshus...@gmail.com> wrote: >> The build process for the site is very old -- is that still applicable >> after the svnpubsub change? > > svnpubsub makes it so that whenever you commit to the svnpubsub > directory, those changes are immediately pushed out into the live web > site. > > So it's more of a change in how pages are published than a change in > how pages are created. I haven't looked that the build process for > the site, but I would guess only the deployment stage needs to be > updated. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
