Hi, As you perhaps noticed, I migrated also the PDFBox site build from Ant to Maven and updated the site layout a bit along the way. Site sources are still in the xdoc format, they've just moved from src/documentation/content/xdocs to src/site/xdoc. To build the site, use "mvn site" instead of "ant website".
This is not the only change I have in mind, read on... On Fri, Feb 12, 2010 at 11:45 AM, Jukka Zitting <[email protected]> wrote: > We currently generate the live web site from the PDFBox trunk, so we > should only change these once the 1.0.0 release is officially out. > This does cause the inconvenience of having to have outdated > information in the release package. Perhaps we should move the PDFBox > site sources to a separate svn subtree. This has been on my mind for a while. It would be nice if we could keep full copies of the documentation (javadocs and all) of all past major releases. However, keeping all that stuff in the latest trunk quickly gets pretty heavy, so I'd like to repurpose the currently unused site directory in https://svn.apache.org/repos/asf/pdfbox/site for this. The latest product documentation would still be kept in the trunk and would be copied into the published site as a per-version subtree (http://pdfbox.apache.org/1.0/, etc.) for all major and minor releases (not for patch releases, as they shouldn't introduce any new API). Project information like latest news and pointers to mailing lists and the issue tracker would only be kept in the site directory, i.e. not in the trunk. With this proposed change I'd also like to migrate to use the new svnpubsub site publishing mechanism created by the infra team. With that the compiled site is committed to svn along with the site sources, and the svnpubsub system takes care of making the committed changes instantly visible on the web. WDYT? BR, Jukka Zitting
