Carsten Ziegeler wrote: > David Crossley wrote: > > > > Why do we need DTDs to be included here? If they need to be in Cocoon > > CVS, then shouldn't they be in WEB-INF/entities. > > The validate-xdocs task validates all our documents and uses the > DTDs from the documentation directory. As the "old" document-10 dtd > was already there, I thought it would be the natural place to put > the newer dtd.
Since we use the entity resolver, the main location for DTDs is over at WEB-INF/entities and they need to be added to the "catalog". The set of DTDs at xdocs/dtd/ is a relic from before we had the entity resolver. We should actually nuke the latter set ... too many copies of them. Yes i now see the problem with 'validate-xdocs'. > Now, I guess if we are using forrest for document generation we > could completly remove the DTDs and the validation task as well > as forrest will do that for us. We are in a bind there. Even if we do use Forrest for the command-line docs building, then we still have the documentation in the webapp which does not use Forrest. I am not sure what the answer is here. --David
