This might be a silly/dumb question, but why does the site doc generation have to be so complicated; i.e. using Cocoon. I know there is one PDF in there, but other than that, why can't it just be a simple XML > XSLT > HTML transform? Does all of Jakarta generate their docs the same way Avalon does?
- Robert -----Original Message----- From: Leo Simons [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 4:55 AM To: Avalon Development Subject: documentation generation can we please standardize on this across the board? I am at a point where I really don't care anymore what the docs look like or what is used to generate them, just as long as it works. But we currently have cocoon (customized), jakarta-site (customized), and jakarta-site2 in use in various places, all of them broken to a degree. I spent about an hour yesterday trying to get cocoon working for tweety doc generation, gave up, then tried to copy the doc generation bits from phoenix, and ended up with a log containing around 50 velocity errors. I feel sorry for raising the subject, as we're only off worse now than a few months ago. If we go further down this path I'm gonna drop java alltogether and focus on something silly like PHP :/ If you were to ask me now, we should remove dependencies on everything but jakarta-site2 and just live with the #*%!@ html it spits out. It is the only thing so far that works well. regards, - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
