8356629: Incorrect use of {@linkplain} in java.sql

[nizarbenalla]

Please review this trivial patch to fix a javadoc bug.

TIA

---

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-8356629: Incorrect use of {@linkplain} in java.sql (Sub-task - P4)

Reviewers

• Lance Andersen (@LanceAndersen - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25286

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

@nizarbenalla 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:

8356629: Incorrect use of {@linkplain} in java.sql

Reviewed-by: lancea

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 111 new commits pushed to the master branch:

• b07da7b: 8357171: Test tools/jpackage/windows/WinOSConditionTest.java fails for non administrator
• d0402dd: 8355323: JShell LocalExecutionControl should add stopCheck() at method entry
• 48df41b: 8357306: G1: Remove _gc_succeeded from VM_G1CollectForAllocation because it is always true
• ... and 108 more: https://git.openjdk.org/jdk/compare/76570c627db527f856f2394fb9ead02939eca621...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.

[openjdk]

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

• core-libs

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 (1fc5ac58)

[nizarbenalla]

Thanks for the review

/integrate

[openjdk]

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

• b037353: 8357081: Removed unused methods of HexDigits
• 1f24a54: 8357644: Add missing CPE statements
• e893305: 8334513: New test gc/TestAlwaysPreTouchBehavior.java is failing on MacOS aarch64
• ... and 121 more: https://git.openjdk.org/jdk/compare/76570c627db527f856f2394fb9ead02939eca621...master

Your commit was automatically rebased without conflicts.

[openjdk]

@nizarbenalla Pushed as commit b034710.

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