-
Bug
-
Resolution: Unresolved
-
P4
-
9, 10, 11, 12, 13
-
None
This is a result of an email discussion on running javadoc on src.zip
http://mail.openjdk.java.net/pipermail/javadoc-dev/2018-August/000639.html
The bottom line is that running javadoc in the simple/obvious way (NOT just "make docs") results in 918 warnings, mostly caused by bad doc comments. The list is attached.
java.base 254
java.compiler 1
java.datatransfer 1
java.desktop 189
java.instrument 1
java.logging 3
java.management 117
java.management.rmi 2
java.naming 25
java.net.http 7
java.prefs 1
java.rmi 19
java.scripting 2
java.se 2
java.security.jgss 20
java.security.sasl 3
java.sql 6
java.sql.rowset 31
java.transaction.xa 1
java.xml 303
java.xml.crypto 9
The bug is filed here as a placeholder; we should create subtasks for various subsets of the modules, to render the work more manageable.
http://mail.openjdk.java.net/pipermail/javadoc-dev/2018-August/000639.html
The bottom line is that running javadoc in the simple/obvious way (NOT just "make docs") results in 918 warnings, mostly caused by bad doc comments. The list is attached.
java.base 254
java.compiler 1
java.datatransfer 1
java.desktop 189
java.instrument 1
java.logging 3
java.management 117
java.management.rmi 2
java.naming 25
java.net.http 7
java.prefs 1
java.rmi 19
java.scripting 2
java.se 2
java.security.jgss 20
java.security.sasl 3
java.sql 6
java.sql.rowset 31
java.transaction.xa 1
java.xml 303
java.xml.crypto 9
The bug is filed here as a placeholder; we should create subtasks for various subsets of the modules, to render the work more manageable.
- relates to
-
JDK-8213817 @return has already been specified (4 occurrences, in AWT and Swing)
-
- Resolved
-
-
JDK-8213819 doclint should warn against {@index} inside <a> tag
-
- Resolved
-
-
JDK-8213818 @return has already been specified
-
- Closed
-
-
JDK-8213820 unknown tag: @returns
-
- Closed
-