I will not have much time to help with the docs re-organisation, but i will do what i can.
Here is a list of the changes that i have made to the forrestbot configuration. For those that didn't know about it, there is a demonstration Forrestbot which automatically builds the documentation every six hours. Cocoon committers can also trigger it manually. http://brutus.apache.org:36366/forrestbot-webapp/ cocoon-block-portal ------------------- This was called "cocoon-doco-portal" which used sources from http://svn.apache.org/repos/asf/cocoon/whiteboard/doc-repos/portal-block Now it has been renamed to "cocoon-block-portal" and uses sources from http://svn.apache.org/repos/asf/cocoon/trunk/src/blocks/portal/documentation Is each block going to have a separate forrest configuration? cocoon-doco-global ------------------ This uses sources from http://svn.apache.org/repos/asf/cocoon/whiteboard/doc-repos/global This is the new whiteboard docs for the top-level Cocoon website. cocoon-site ----------- This uses sources from http://svn.apache.org/repos/asf/cocoon/site This is the current docs for the top-level Cocoon website. Is "cocoon-doco-global' supposed to replace this? cocoon-trunk ------------ This was the documentation for trunk 2.2 docs. I don't want to remove the forrestbot configuration for this, because it was a huge effort to get it to build. We might need some of this configuration for the new "cocoon-2-2" docs when it is building the "userdocs" again. The forrestbot builds have been disabled. cocoon-2-2 ---------- This was called "cocoon-doco-2-2" which used sources from http://svn.apache.org/repos/asf/cocoon/whiteboard/doc-repos/2.2 Now it has been renamed to "cocoon-2-2" and uses sources from http://svn.apache.org/repos/asf/cocoon/trunk/src/documentation which replaced the original content. -------------------------------- People can still build each site locally (need forrest-0.6+ installed). e.g. cd trunk/src/blocks/portal/documentation; forrest e.g. cd trunk/src/documentation; forrest Reinhard, when you are back, we can try to fix the building of the "userdocs" and installing/jars.html in "cocoon-2-2" ... --David Reinhard Poetz wrote: > David and I have talked what has to be done to integrate the automatically > generated docs into the new docs repository. He reminded me that we > shouldn't lead this discussion in private but on [EMAIL PROTECTED] (Sorry > guys, > it started with a slightly off-topic question and it has grown bigger, and > bigger ....) > > David Crossley wrote: > > Reinhard Poetz wrote: > > >> After looking at cocoon/trunk/tools/targets/docs-build.xml I have to > admit that I don't understand the purpose of this, except that it builds > the sitemap-components docs. > > > > It copies all the source xml docs to a work directory, generates the > > important source for installing/jars.xml file, runs the SitemapTask to > > read the userdocs/*/*.xml and append other content that gets generated > > from the java sources, and i think that it might also copy the generated > > javadocs. Then the user runs 'forrest' which is configured in > forrest.properties > > to read the sources from the temporary directory which was generated by > > the 'build docs'. The process to build > > I cannot properly see from here, but if you have re-arranged the location > > of the sources, then the cocoon/trunk/forrest.properties will need to be > > modified. The forrestbot config might not need to be changed. > > > > There is no point making changes to the forrestbot until this > > can be run locally. If you can do 'build docs; forrest' . > > I'm going to be off-line until Wednesday next week, but then I will have a > look again at the doc target and will try to fix it. If somebody misses the > old 2.2 documentation - it moved to cocoon/whiteboard. > > -- > Reinhard P?tz Independant Consultant, Trainer & (IT)-Coach > {Software Engineering, Open Source, Web Applications, Apache Cocoon} > > web(log): http://www.poetz.cc > --------------------------------------------------------------------
