Added -quiet option to shut off non-error/warning noise.
Location of fix:
We need to decide on this.
I believe this requires changes to both the javadoc tool and the standard doclet.
We need to decide whether to break "compatibility" and offer a new
option, such as -quiet (suggested by an outside developer),
or modify -verbose so the default is not to show those "processing"
and "generating" messages. Only the -quiet option would maintain
compatibility, but would be different from javac, which is quiet
by default. (I notice that javac displays no parsing/loading/writing
messages without -verbose, but with -verbose displays them with millisec.)
There is a lot of value in the current default messages, as it
shows the status/progress of javadoc. I would not want these messages
to be merged with the current -verbose messages (for the following
reasons). We may need two levels of verbose, which is achieved
with either -quiet or by adding a variant of -verbose.
The first disadvantage to the current -verbose is that it seems to
take 30 seconds before the first message is displayed, compared to
2 seconds without -verbose. It's doing something up-front.
Secondly, -verbose currently adds messages showing each .class
file it loads and how many millisecs it takes to load each one.
When documenting the simple com.package1 and com.package2 sample packages,
this ends up with 72 messages compared to 23 messages without -verbose.
Here are the kinds of messages -verbose displays:
Loading source files for package com.package1...
[parsed ./test/sample-src/com/package1/Interface1.java in 423 ms]
[parsed ./test/sample-src/com/package1/SubClass1.java in 97 ms]
[parsed ./test/sample-src/com/package1/Class1.java in 26 ms]
Constructing Javadoc information...
rt.jar(java/lang/Object.class) in 28 ms]
So we should not simply move the "processing" and "generating" messages