United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-4702454 : tool: -quiet should suppress non-error/warning messages in javadoc tool

Details
Type:
Enhancement
Submit Date:
2002-06-14
Status:
Resolved
Updated Date:
2004-02-20
Project Name:
JDK
Resolved Date:
2004-02-20
Component:
tools
OS:
other
Sub-Component:
javadoc(tool)
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
1.4.1
Fixed Versions:
5.0 (b40)

Related Reports

Sub Tasks

Description
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
import Server;
             ^
1 error

==========================================================
-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...

Comments
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
tiger-beta2

FIXED IN:
tiger-beta2

INTEGRATED IN:
tiger-b40
tiger-beta2
2004-06-14 
EVALUATION

Because that is an option to the standard doclet.  The standard doclet
is not printing those messages, the tool is.

Part of the problem is the documentation for the -quiet option, which
implies that it would suppress messages from the tool, which it cannot.

This is not a bug, though perhaps a reasonable feature request.

###@###.### 2002-06-14

Related bugs are:
   4714350 where the documentation incorrectly states that all messages are 
           suppressed (which will be true once this bug is fixed)
   4431712 an obsolete proposal to move messages to the -verbose option

When neither -verbose nor -quiet are specified, the behavior should be
unchanged from its current behavior.  When both are specified, I suggest
we throw an error and do not continue, with an error message such as:

   error: cannot continue with both options: -verbose -quiet

###@###.### 2002-07-25
2002-07-25


Hardware and Software, Engineered to Work Together