Why am I getting the first two lines when I run javadoc -quiet:
Loading source file Access.java...
Constructing Javadoc information...
.\Client.java:11: '.' expected
-quiet just isn't useful (to me, at least), unless it actually
prevents *all* non-error/warning messages. The idea is to be
totally silent unless there is a problem -
that way, an output scraping script (for instance) can tell if the run
was clean (or not). Without a functionally quiet behavior, such a
script is required to actually parse the output line-by-line to decide
if it is something a human needs to see. In my case, we build several
branches of a 1MLOC application on an hourly basis continuously - it is
*really* important that the build results analysis tool not complain
about false positives. Any such long-term leaks end up with the
developers ignoring the messages and thus missing real problems...