-
Bug
-
Resolution: Fixed
-
P4
-
22, 23
-
None
-
b12
Currently in the javadoc tool, the generated class use page does not track the occurrences of a class in the type arguments of the extends or implements list, where they can appear. For example:
public class One {}
import java.util.*;
public class Two extends ArrayList<One> implements Comparator<One> {
}
Run `javadoc -use *.java`, the use page for One will be empty, despite it appearing in the type arguments.
This problem already manifests itself in the current JDK 22: The preview class java.lang.classfile.FieldBuilder has a usage in FieldTransform (which extends ClassFileTransform<FieldElement, FieldBuilder>) but is not shown as such. It limits the usefulness of use page as a way to examine the API exposure of a class without using IDEs.
public class One {}
import java.util.*;
public class Two extends ArrayList<One> implements Comparator<One> {
}
Run `javadoc -use *.java`, the use page for One will be empty, despite it appearing in the type arguments.
This problem already manifests itself in the current JDK 22: The preview class java.lang.classfile.FieldBuilder has a usage in FieldTransform (which extends ClassFileTransform<FieldElement, FieldBuilder>) but is not shown as such. It limits the usefulness of use page as a way to examine the API exposure of a class without using IDEs.
- links to
-
Commit openjdk/jdk/3a00fc73
-
Review(master) openjdk/jdk/17414