On 12/12/2010 12:12 PM, Peter Firmstone wrote:
Ok, sounds logical, when you checkout and build River, all the documentation is build able from ant, which is then included in the build that I release, so the copy we build for the website should also be buildable from ant? Does this mean we need a new tool in our lib's to build the docs?
Could be, yes. We could decide to include the docs in original markdown format, or scrape them from the website, or convert them to html by markdown. The only quick solutions that i see are include the original mdtext files, or pull the converted mdtext files from the svn repo that contains the website just before publishing (all html).
Gr. Sim the chain is as follow for ASF CMS: mdtext in svn stage: convert to html store html in website repo checkout to staging website publish: copy html in website repo to other repo dir chechout to production website (all the mirrors)
