-
Bug
-
Resolution: Fixed
-
P3
-
13
-
b13
The new/revised guidelines are:
* Headings in documentation comments for all modules, packages and types (including nested types) shuld begin at <h2>.
* Headings in members should begin at <h4>.
Previously, and incorrectly, doclint assumed that all headings should begin at <h3>, and while it checked for messing headings, it did not check for low headings.
- duplicates
-
JDK-8220454 update doclint to better check for headings in doc comments
-
- Closed
-
-
JDK-8216463 rename "header" to "heading" in doclint
-
- Closed
-
- relates to
-
JDK-8220249 fix headings in java.compiler
-
- Resolved
-
-
JDK-8220250 fix headings in java.desktop
-
- Resolved
-
-
JDK-8220251 fix headings in java.management
-
- Resolved
-
-
JDK-8220257 fix headings in java.instrument
-
- Resolved
-
-
JDK-8233338 FX javadoc headings are out of sequence
-
- Resolved
-
-
JDK-8220252 fix headings in java.naming
-
- Closed
-
-
JDK-8220253 fix headings in java.sql.rowset
-
- Closed
-
-
JDK-8220256 fix headings in java.security.sasl
-
- Closed
-
-
JDK-8220258 fix headings in java.smartcardio
-
- Closed
-
-
JDK-8220261 fix headings in java.base
-
- Closed
-
-
JDK-8220262 fix headings in java.logging
-
- Closed
-
-
JDK-8284774 Use headings and provide anchors in Document interface
-
- Open
-
-
JDK-8223552 change in implicit header nesting breaks backwards compatibility
-
- Closed
-
-
JDK-8220248 fix headings in java.util.concurrent
-
- Closed
-
-
JDK-8220254 fix headings in java.xml
-
- Closed
-