Vincent Massol wrote:
Hi Chris,Hmm, there could probably be an <uptodate> check to perform the <xmlvalidate>-task conditionally based on a prior transform... however, if it's the <style>-task that now takes longer, there's not much we can do except to remove the DTDs (AFAIK).
I'm not 100% sure but it seems that the introduction of DTDs has slowed
the web site generation by a factor 2 or 3 at least. "ant clean dist"
now takes 2 minutes and 17 seconds on my machine (I think it was taking
something like 30-40 seconds before).
Do you have any idea how we could speed it up?
Actually, there have been many changes to the documentation build, as you know. We're compiling Java code, running the <checksitemap> task, and the stylesheets have become more complex (the document() calls would have the most significant impact on performance).
I currently don't have time to look into this, but if it's the addition of the DTD and validation, I'd be against removing it again. The benefit validation brings, in combination with the other checks we now have in place, is better quality control over the docs, and the ability to see the scope of changes. I.e. if all documents comply to their respective DTDs, they are also guaranteed to work with the XSLT stylesheets, etc.
BTW, if we bring PDF generation into the game, the numbers you posted will look quite unrealistically low ;-)
--
Christopher Lenz
/=/ cmlenz at gmx.de
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
