Andreas Hochsteger wrote: >> Something like a list of referenced internal and external documents >> or link checking comes to my mind.
Internal link checking happens during the "build docs". If you have the wrong filename in a link, then it will report errors. This is why it is very important to run "build docs" before preparing a patch. External link checking is another matter and is a very specialised task. We run the excellent LinkAlarm service over the Cocoon website after each release so that errors can be fixed before the next release. For some reason the README docs about this were recently removed from CVS. I just added them back and scheduled LinkAlarm to do its magic over the recent 2.0.2 release. I will send cocoon-* lists an announcement when it is done and we can all help to fix. >> Perhaps the Forrest project provides something like that, but I >> couldn't find any information about it yet. It seems that there only >> exists a cvs repository, so a little information about it would be helpful. Apache Forrest is a fledgling project and there is no website yet. This is yet another call for people to come and help us. --David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
