|
Description
|
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 :
javadoc is examining (and doing something erroneous)
with jar files in the classpath, without any reference from
the source files being javadoced.
I've used jar to package a single set of files as
examples for all the associated bug reports.When running javadoc in a large autobuild process, I see a number of messages like:
server.jar: Body tag missing from HTML
1 error
Oddly, the jar file referred to by the error message is, in
this case, unreferenced by the source files and packaged
being javadoced. Why is javadoc examining jar files which
have no relevance to the sources?
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
Loading source files for package org.cougaar...
Constructing Javadoc information...
server.jar: Body tag missing from HTML
1 error
# test 2
% rm -rf api; mkdir api
% javadoc -quiet -d api -sourcepath src org.cougaar
Loading source files for package org.cougaar...
Constructing Javadoc information...
EXPECTED VERSUS ACTUAL BEHAVIOR :
Actual:
see above
Expected:
the same output - the classpath should make no difference in
the javadoc run of this one source file.
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: 146959)
======================================================================
|
