Hi Ferdinand, i wonder if you have set xml validation off in the forrest.properties file. There are errors in the new How_to_release.xml xdoc.
More than that, this stops other people from working with the docs. Sorry to make an example of this, but it is very important for collaborative development. -David > Author: crossley > Date: Mon May 22 15:55:10 2006 > New Revision: 408778 > > URL: http://svn.apache.org/viewvc?rev=408778&view=rev > Log: > Plead with people to validate their xml source changes. > > Modified: > forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml > > Modified: > forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml > URL: > http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml?rev=408778&r1=408777&r2=408778&view=diff > ============================================================================== > --- > forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml > (original) > +++ > forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml > Mon May 22 15:55:10 2006 > @@ -27,7 +27,7 @@ > > <section id="About"> > <title>About this Document</title> > - <fixme author="fso">This is work in progress!</fixme> > + <fixme author="open">This is work in progress!</fixme> > </section> > > <section id="OrgDoc"> > @@ -50,6 +50,14 @@ > > > # Make changes to sources, and then test, then commit. > + > + # Please, please, ensure valid xml docs. Errors will be > + # reported during the 'build' phase if you don't. > + # You can do 'forrest validate-xdocs" beforehand or use > + # a validating editor (link: catalog.html) or for a single > doc use > + # xmllint (link: catalog.html) from the command-line, e.g. > + # xmllint --noout --valid --catalogs faq.xml > + > # Use the forrestbot to build and then deploy to > svn.apache.org ... > > cd site-author >
