Name: gm110360 Date: 06/04/2002

FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)


FULL OPERATING SYSTEM VERSION :
generic

ADDITIONAL OPERATING SYSTEMS :

Linux draught.bbn.com 2.4.19-pre8 #1 SMP Tue May 21 14:23:08
EDT 2002 i686 unknown

A DESCRIPTION OF THE PROBLEM :
I've used jar to package a single set of files as
examples for all the associated bugs.

When running javadoc in a large autobuild process, I see a
number of messages like:
  server.jar: Body tag missing from HTML
  1 error
Note that the message printed does not actually contain the
word "error" even though it is counted as an error in the
final error/warning sum. Also odd is that it is counted as
an error even though it is not fatal and apparently has no
impact on the output files. Other javadoc error messages
include the word "error" and warning messages, "warning".
This makes it difficult for build scripts to screen output
for errors correctly.

  Bug 2: This bug report is complaining that the actual error
message does not include the word "error"

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
The minimal examples may be found at:
http://www.alpine.bbn.com/~mthome/javadocbug.jar
grab the the above file and unpack it into a clean directory
of your choosing. It contains some .java files and some
.jar files used in the various "steps to reproduce" sections.
% cd /tmp/foo
% jar xf /tmp/javadocbug.jar
% mkdir api
# test 1
% javadoc -classpath server.jar -quiet -d api -sourcepath
src org.cougaar


EXPECTED VERSUS ACTUAL BEHAVIOR :
Actual:
Loading source files for package org.cougaar...
Constructing Javadoc information...
server.jar: Body tag missing from HTML
1 error

Expected:
A message more like "Error: server.jar: foo.html: Body tag
missing from HTML"

ERROR MESSAGES/STACK TRACES THAT OCCUR :
server.jar: Body tag missing from HTML

This bug can be reproduced always.

---------- BEGIN SOURCE ----------
not relevant. The source code used in the example can be anything at all to
generate the same error.
---------- END SOURCE ----------
(Review ID: 146958)
======================================================================