JDK-8319988: Wrong heading for inherited nested classes

[hns]

Please review a trivial fix to make javadoc use the correct heading for listings of inherited nested classes.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8319988: Wrong heading for inherited nested classes (Bug - P4)

Reviewers

• Jonathan Gibbons (@jonathan-gibbons - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16641/head:pull/16641
$ git checkout pull/16641

Update a local copy of the PR:
$ git checkout pull/16641
$ git pull https://git.openjdk.org/jdk.git pull/16641/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 16641

View PR using the GUI difftool:
$ git pr show -t 16641

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16641.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back hannesw! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@hns The following label will be automatically applied to this pull request:

• javadoc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (200786ff)

[openjdk]

@hns This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8319988: Wrong heading for inherited nested classes

Reviewed-by: jjg

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 89 new commits pushed to the master branch:

• a2c0fa6: 8320372: test/jdk/sun/security/x509/DNSName/LeadingPeriod.java validity check failed
• 3aefd1c: 8320234: Merge doclint.Env.AccessKind with tool.AccessKind
• d6d7bdc: 8319817: Charset constructor should make defensive copy of aliases
• 0712b22: 8320147: Remove DumpSharedSpaces
• 6e86904: 8319973: AArch64: Save and restore FPCR in the call stub
• 04fd17e: 8320410: Reflow markdown in building.md
• 7f23110: 8319928: Exceptions thrown by cleanup actions should be handled correctly
• a6098e4: 8320280: RISC-V: Avoid passing t0 as temp register to MacroAssembler::lightweight_lock/unlock
• 60c8d9c: 8320300: Adjust hs_err output in malloc/mmap error cases
• 9f6a4a3: 8320386: Remove java/nio/channels/vthread/BlockingChannelOps.java#direct-register from ProblemList
• ... and 79 more: https://git.openjdk.org/jdk/compare/d992033439073d35877a2c0296fbd01ad5cbcb07...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[hns]

/integrate

[openjdk]

Going to push as commit cee54de.
Since your change was applied there have been 90 commits pushed to the master branch:

• 32098ce: 8320348: test/jdk/java/io/File/GetAbsolutePath.windowsDriveRelative fails if working directory is not on drive C
• a2c0fa6: 8320372: test/jdk/sun/security/x509/DNSName/LeadingPeriod.java validity check failed
• 3aefd1c: 8320234: Merge doclint.Env.AccessKind with tool.AccessKind
• d6d7bdc: 8319817: Charset constructor should make defensive copy of aliases
• 0712b22: 8320147: Remove DumpSharedSpaces
• 6e86904: 8319973: AArch64: Save and restore FPCR in the call stub
• 04fd17e: 8320410: Reflow markdown in building.md
• 7f23110: 8319928: Exceptions thrown by cleanup actions should be handled correctly
• a6098e4: 8320280: RISC-V: Avoid passing t0 as temp register to MacroAssembler::lightweight_lock/unlock
• 60c8d9c: 8320300: Adjust hs_err output in malloc/mmap error cases
• ... and 80 more: https://git.openjdk.org/jdk/compare/d992033439073d35877a2c0296fbd01ad5cbcb07...master

Your commit was automatically rebased without conflicts.

[openjdk]

@hns Pushed as commit cee54de.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.