Hi Jonathan, > We could move back to the earlier tool chain (ant, Saxon, Xerces, > DocBook DTDs, DocBook stylesheets.
I'm hoping you can help me out here... When I see documentation sources checked in and mention of a way to build them, I think there must be some defined tools that build the docs. Analogous to a C++ compiler, linker, etc. And since I don't need to worry about downloading or committing a C++ compiler to svn, I'm confused about why this issue keeps coming up. > Instead of checking these things into subdirectories, I could > put them > in a zip file in my people.apache.org account, and create an ant task > that retrieves them and unzips them into the right subdirectories. > > For people like Rafi who do not want multiple copies on their > system, I > could write a shell script that creates symbolic links to the > standard > installed locations. People can modify this as needed if they > have these > things installed elsewhere. > > That's the best I've thought of so far. > > Thoughts? I should probably go look at what's checked in first, but... Is there a defined set of tools for building the docs? Is there a reason you can't put a README there with a list of what's needed, and let people get it whatever way works best? I would like to be able to work on the documentation at some point, so I am interested in getting this worked out. Thanks, -Steve --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
