title: Measuring Documentation Coverage with Javadoc and Ant
body: <p>I am involved in a project in which public API documentation is a clear deliverable.  In order to ensure that the release meets this requirement, I'd like to ensure that the the release target in my Ant build file fails if documentation coverage is too low.</p>
  
  <p>As a minimum, each identifier with public or protected access should have appropriate Javadoc tags and a description.  For example, public methods should have a <code>@param</code> tag for each parameter, a <code>@return</code> tag if the return type is not <code>void</code>, a <code>@throws</code> tag for each exception, and a single line description.</p>
  
  <p>I currently have JUnit code coverage reports and failure conditions using Cobertura, so something similar to that for documentation would be perfect.  However, if the detection of a failure condition is not available, a report be a reasonable substitute.</p>
  
  <p>The documentation <strong>must</strong> be in Javadoc format.  No other format -- including Doxygen -- is acceptable.</p>