<http://hackystat.ics.hawaii.edu/hackystat/controller?Page=help&Subpage=toc>
You'll also notice that there's a new section called "Sensor Download File Index", which provides direct links to the top-level files in the download/ directory. This makes it easier for people to get a new copy of a jar file when they know what they're doing. I've wanted this for a while and decided to do it since I was rewriting that page anyway.
There is one major bummer: because of some embedded classloader craziness in the DocBook Ant task, you can't build the docbook documentation and then run JUnit during the same Ant invocation. (Basically, the Docbook task seems to load some kind of SAX class which blows away JUnit.) So, for cruisecontrol, the DocBook generation task runs after JUnit as part of distAll which keeps it out of trouble. The point is, if you are doing local development, you'll want to test in the following way:
hackyBuild> ant -q freshStart junitAll # to check that everything else is OK. hackyBuild> ant -q buildDocBook # to check that docbook runs successfully
You can run these targets in either order for testing purposes, but to actually see the documentation in the running instance of the webapp, you need to do the buildDocBook target second (since freshStart deletes the build/ directory).
The conversion is not yet complete: there's a bunch of suddenly vestigial code in the system pertaining to the old documentation that I need to clean out.
Oh, and the daily build doesn't generate docbook files in the right place right now. I need to fix that too.
Take a look, let me know what you think. There's a bit of a learning curve involved in doing this and (with apologies) I haven't yet written any DocBook documentation on generating DocBook documentation. Talk to me directly if you want some help getting started.
Cheers, Philip
