-
Enhancement
-
Resolution: Duplicate
-
P4
-
None
-
1.2.0, 1.3.0
-
None
-
generic, sparc
-
generic, solaris_2.6
In 1.3, for @see to link to an external referenced class, that class
must appear somewhere in a signature or explicitly in an import statement.
This means many links do not appear unless someone examines the HTML
pages to see if links actually were generated. It also means someone
must add such a reference (such as "import java.lang.SecurityManager")
just to make the link appear. These are difficult constraints to
live with.
With javadoc built on the new compiler, can it be redesigned so that @see or {@link} itself will be a sufficient reference to allow -link to create links? If not, can Javadoc be redesigned to enable linking to any classes that are referenced in the *implementation*?
must appear somewhere in a signature or explicitly in an import statement.
This means many links do not appear unless someone examines the HTML
pages to see if links actually were generated. It also means someone
must add such a reference (such as "import java.lang.SecurityManager")
just to make the link appear. These are difficult constraints to
live with.
With javadoc built on the new compiler, can it be redesigned so that @see or {@link} itself will be a sufficient reference to allow -link to create links? If not, can Javadoc be redesigned to enable linking to any classes that are referenced in the *implementation*?
- duplicates
-
JDK-4349894 javadoc referenced classes do not include classes in method bodies
-
- Closed
-
-
JDK-4330419 With -link, @see/@link don't create links to imported classes
-
- Closed
-