I am now able to build the default & printable manuals consitently by using the SAXON XSLT. I had to force it to be used by setting the system property, since there is no easy way to plug it into the style task, with out writting some XSLTLieason (or whatever it is called) class. Perhaps the ant docs are off... I didn't want to waste any more time. I cleaned up organization of the xml & static/images sources to make it easier on the build system. I am still having some issues with older xerces parser crashing the jvm on my redhat 7.0 box, and the latest xerces beta 2 doesn't seem to like the SAXON XSLT very much, so we are still using crimson as the default parser. Here is the changelog: o moved xml docs to xdocs to make the build a little easier & seperate things a little bit. o moved howto docs to xdocs/howto o renamed jboss.xsl to fancy.xsl o added plain.xsl & printable.xsl o changed html-* targets to docs-html-* for consitency o using SAXON for XSLT for all docs-html-* targets o docs-html will now build the fancy and printable docs by default, use the docs-html-plain for the basic chunked docbook format (minus the jboss fancy header and footer). Fop still dosen't work, I tried a cvs snapshot for kicks and still no luck. I don't plan on trying any futher on this. I could not even get the native docbook2pdf converter to generate a pdf from this. Any ways, let me know if you have any issues building this. It does complain a little about some entity fluff, but it keeps on generating docs, which is all I care about at this point. If you happen to know what the errors mean and have the capacity to fix them, be my guest, just let me know what ya did so I can make it a learning experence. --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
