Audited Objects Build Tool

This is the documentation for Audited Objects. For an introduction to what AO does, start with the Synopsis, then download the full install package or just a client binary, or get the source code.

To install AO for the first time, see the Installation instructions. If updating, see also the release notes. To install or update just a client, see the current set of AO Client Packages. Once server and client are installed and working you may want to look through the Tour Through Audited Objects and have a look at the FAQ.

Full Documentation Set

ao-changes	AO Change Log
ao-install	AO Installation Guide
ao-tour	Tutorial Introduction to AO
ao man page	The AO Client Manual Page
ao-faq	Frequently Asked Questions
ao-future	Thoughts and Plans for AO Future
ao-howto	Help Getting Started
ao-make	Notes on Using AO with make
ao-properties	Client Property Settings
ao-tuning	Tips on Tuning a Build for AO
ao-clearmake	Comparison of AO with Clearmake
ao-ccache	Comparison of AO with ccache
ao-vcs	Discussion of AO Integrations With Version Control Systems
ao-teamconcert	Discussion of AO Integration with IBM Rational Team Concert
ao-ide	Discussion of Potential AO Integrations with IDEs
ao-buildmodels	Philosophical Considerations of Competing Build Models
ao-developers	Overview of Internal AO Design and Coding Concepts
ao-license	AO Licensing

Out of the box the AO server runs in evaluation mode, meaning that its data is retained only as long as the server is running. Turning on full persistence involves setting a few properties.
The Audited Objects tool set is still young; nothing here should yet be considered production quality. The Windows client is in an alpha state and has had only proof-of-concept testing. Also, no guarantee of compatibility is made between this and any subsequent releases, though there is no plan for incompatible changes.
While the Linux client is fairly stable, the Java server is known to be actually broken and its use is deprecated. See the futures document for details. There are things that can be done with just the client but client-server use is hobbled until I (or someone) can find time to fix or rewrite it.
The author may be reached via boyski@users.sourceforge.net.