On Saturday, March 22, 2003, at 09:14 AM, Stephan Michels wrote:
No, I mean not ignoring for the validation, I mean ignoring for the documentation generation process.
At the moment you couldn't generate the docs by Cocoon. I want to make the
step invasive as less as possible.
Stephan, many thanks for your work on this.
I had this same problem the last time I did this. It appears that no more than one sitemap.xmap can exist in the same project.content-dir, even if it has a different name. Thus, to have Forrest ignore Cocoon's existing sitemap, we have to rename it. But this breaks the existing Cocoon docs build because it can't find the (renamed) sitemap.
Diana
