Name: bsT130419			Date: 09/26/2001


java version "1.4.0-beta2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta2-b77)
Java HotSpot(TM) Client VM (build 1.4.0-beta2-b77, mixed mode)


If you have a package named "java" (obviously not a top-level package), then
javadoc reports an error when constructing the javadocs.

e.g:

package a.java;
public class A {
}


Using the 1.4 javadoc command gives:

[len@nepenthes java_test]$ javadoc -d doc a.java
Loading source file a.java...
error: cannot read: a.java
1 error

Using the 1.3 javadoc command gives:
[len@nepenthes java_test]$ javadoc -d doc a.java
Loading source files for package a.java...
Constructing Javadoc information...
Building tree for all the packages and classes...
Building index for all the packages and classes...
Generating doc/overview-tree.html...
Generating doc/index-all.html...
Generating doc/deprecated-list.html...
Building index for all classes...
Generating doc/allclasses-frame.html...
Generating doc/index.html...
Generating doc/packages.html...
Generating doc/a/java/package-summary.html...
Generating doc/a/java/package-tree.html...
Generating doc/a/java/package-frame.html...
Generating doc/a/java/A.html...
Generating doc/serialized-form.html...
Generating doc/package-list...
Generating doc/help-doc.html...
Generating doc/stylesheet.css...
and generates the expected documentation.
(We have a package named java to implement a custom url protocol named java:,
and having a package named after the protocol is one method for registering such
protocols)
(Review ID: 132606) 
======================================================================