JDK-8288692: jdk/javadoc/doclet/testTagMisuse/TestTagMisuse.java fails after JDK-8288545

[jonathan-gibbons]

Please review a simple fix to address an NPE that can occur with a bad (empty) {@link} tag.

---

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-8288692: jdk/javadoc/doclet/testTagMisuse/TestTagMisuse.java fails after JDK-8288545

Reviewers

• Pavel Rappo (@pavelrappo - Reviewer) ⚠️ Review applies to bfda2d52

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 37

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk19/pull/37.diff

[bridgekeeper]

👋 Welcome back jjg! 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]

@jonathan-gibbons 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

• 01: Full - Incremental (d036bbd1)
• 00: Full (bfda2d52)

[pavelrappo]

Assuming it passes tier1, looks good.

[openjdk]

@jonathan-gibbons 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:

8288692: jdk/javadoc/doclet/testTagMisuse/TestTagMisuse.java fails after JDK-8288545

Reviewed-by: prappo

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 1 new commit pushed to the master branch:

• 97544be: 8268398: 15% increase in JFR footprint in Noop-Base

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

[pavelrappo]

For later. I would be surprised if this could ever happen:

/* DCerroneous, "warning: Tag @throws cannot be used in inline documentation."*/

[jonathan-gibbons]

/integrate

[openjdk]

Going to push as commit f12d044.
Since your change was applied there has been 1 commit pushed to the master branch:

• 97544be: 8268398: 15% increase in JFR footprint in Noop-Base

Your commit was automatically rebased without conflicts.

[openjdk]

@jonathan-gibbons Pushed as commit f12d044.

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