I suddenly realised the issue with "cocoon-trunk". It needs to run its 'build docs' before running 'forrest'. It generates some extra source documentation before forrest starts.
There is a global parameter "forrest-exec" which can call a shell script to do other things, then call forrest.
A better option would be to have the forrestbot buildfile for cocoon-trunk run its 'build docs', then you don't affect any other projects.
I have the forrestbot working now for cocoon-trunk. There is potential to have multiple cocoon-trunk builds running, so i am currently finding a way to avoid that.
--David
-- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http://www.brondsema.net : personal
signature.asc
Description: OpenPGP digital signature
