I'm back working on this and could do with some pointers. Please see below for some of the keys areas.
I've looked closely at your references and read both the forrestbot "svn" workstage and forrestbot automated build and deploying documentation. I understand completely how I want this to work and your suggestion for the process of editing sourc, updating the Nutch site, then an additional forrestbot task would update the new /docs directory within our SVN nutch/branches/branch-1.4/docs diretcory. This would then enable devs to simply svn update and any documentation changes would be updated. It would also provide an excellent way of shipping the generated docs with our next release. The parts I am struggling to understand are below:
I gather that you mean the "generated" relevant docs for that version.lewis john mcgibbney wrote:
> Hi all,
> As a project, we are wanting to ship core documentation with the software
> distribution. Currently the Nutch site documentation can be found here ,
> however we would like to start shipping it with our branch-1.4  under a
> new /docs directory.
> I know this is rather trivial and that there must be documentation on it
> somewhere but I have not been able to get my hands on it from the Forrest
> site yet!
> Thanks for any pointers.
>  https://svn.apache.org/repos/asf/nutch/site/
>  https://svn.apache.org/repos/asf/nutch/branches/branch-1.4/
You could use the "Forrestbot" as we do for our Forrest project docs.
How to deploy documentation with the Forrestbot "svn" workstage
In our case we deploy our generated documentation to SVN forrest/site
which gets 'svn up' on people.apache.org to publish our website.
The Nutch project could do that too for your website docs.
Then have another "Forrestbot buildfile" which deploys the relevant
docs to SVN nutch/branches/branch-1.4