On 03/17/2010 11:46 AM, Andrew Stitcher wrote:
I know we've been discussing docs recently, but I was extremely
surprised to see a huge checkin containing tools to "build" the
documentation.
To put it into perspective, the tools in the qpid/docs directory are
larger than the entire C++ source code.
I can't understand the necessity for checking in vast blobs of tools
like this when they are available elsewhere, and even as packages for
Linux distributions.
Jonathan, what's the rationale here?
I wanted to make it easy for anyone to build the documentation, which
requires a certain version of docbook, docbook-xsl, and Apache FOP
version 0.95 (earlier versions were not anywhere near as good).
The alternative would be to have each person who builds install these
things themselves, ensuring that they had the right versions, then
change paths in build.xml. Another alternative would be to use a tool
like Publican - I don't know if there's a way to disable validation, if
there is not, we would have to resolve all dangling links before we
could use that.
These tools will not be changing very often at all, so this is a cost
you incur once when you update. You've seen that cost now, and won't be
seeing it again unless we upgrade a component.
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
