On 8/18/09 5:34 PM, Chris Hostetter wrote:
As a general rule: if the javadoc command generates a warning, it's a
pretty good indication that the resulting javadocs aren't going to
look the way you expect. (there may be lots of places where the
javadocs look wrong and no warning is logged -- b
the scary number for analyzers might be a bit out of date. (hopefully
most of) these were cleaned up with the contrib/analysis javadocs+test
patch this morning.
On Tue, Aug 18, 2009 at 8:34 PM, Chris
Hostetter wrote:
>
> As a general rule: if the javadoc command generates a warning, it's a pretty
As a general rule: if the javadoc command generates a warning, it's a
pretty good indication that the resulting javadocs aren't going to look
the way you expect. (there may be lots of places where the javadocs look
wrong and no warning is logged -- but the reverse is almost never true)
The o
