8356553 : Incorrect uses of {@link} in AbstractQueuedLongSynchronizer and AbstractQueuedSynchronizer

[viktorklang-ora]

I had to tweak the language a bit to better reflect the intent of the text.

---

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-8356553: Incorrect uses of {@link} in AbstractQueuedLongSynchronizer and AbstractQueuedSynchronizer (Sub-task - P4)

Reviewers

• Alan Bateman (@AlanBateman - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25462

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

@viktorklang-ora 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:

8356553: Incorrect uses of {@link} in AbstractQueuedLongSynchronizer and AbstractQueuedSynchronizer

Reviewed-by: alanb

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

• 1a65719: 8357911: JFR: Fix subtle xor method tagging bug
• 016cc4f: 8357830: JfrVframeStream::_cont_entry shadows super-class field
• 4b9290a: 8356647: C2: Excessively strict assert in PhaseIdealLoop::do_unroll
• ... and 45 more: https://git.openjdk.org/jdk/compare/daa8eda530c4c3929c68ace1f1a2d1ed62331584...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]

@viktorklang-ora 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 (14368593)

[nizarbenalla]

Thanks for doing this! There are no longer any links to private types in java.util.concurrent

[viktorklang-ora]

Thanks @nizarbenalla !

@DougLea Do you think this modification is acceptable?

[DougLea]

This seems OK. Maybe needlessly pedantic, but OK :-)

[viktorklang-ora]

@DougLea You know me. :) Thanks for having a look! :)

[viktorklang-ora]

/integrate

[openjdk]

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

• 1a65719: 8357911: JFR: Fix subtle xor method tagging bug
• 016cc4f: 8357830: JfrVframeStream::_cont_entry shadows super-class field
• 4b9290a: 8356647: C2: Excessively strict assert in PhaseIdealLoop::do_unroll
• ... and 45 more: https://git.openjdk.org/jdk/compare/daa8eda530c4c3929c68ace1f1a2d1ed62331584...master

Your commit was automatically rebased without conflicts.

[openjdk]

@viktorklang-ora Pushed as commit 18285fc.

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