8276573: Use blessed modifier order in jdk.javadoc

[pavelrappo]

This PR is to jdk.javadoc as JDK-8276348 (#6213) to java.base. This change was produced by running the below command:

$ sh ./bin/blessed-modifier-order.sh src/jdk.javadoc

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8276573: Use blessed modifier order in jdk.javadoc

Reviewers

• Jonathan Gibbons (@jonathan-gibbons - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6239/head:pull/6239
$ git checkout pull/6239

Update a local copy of the PR:
$ git checkout pull/6239
$ git pull https://git.openjdk.java.net/jdk pull/6239/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 6239

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6239.diff

[bridgekeeper]

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

@pavelrappo 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 (5e59831f)

[openjdk]

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

8276573: Use blessed modifier order in jdk.javadoc

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

• 32895ac: 8275650: Problemlist java/io/File/createTempFile/SpecialTempFile.java for Windows 11

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]

/integrate

[openjdk]

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

• bf4ddf9: 8276338: Minor improve of wording for String.to(Lower|Upper)Case
• afb502e: 8276550: Use SHA256 hash in build.tools.depend.Depend
• 49b7b2e: 8276640: Use blessed modifier order in jfr code
• 5acff75: 8276429: CodeHeapState::print_names() fails with "assert(klass->is_loader_alive()) failed: must be alive"
• a6fa6ed: 8268779: ZGC: runtime/InternalApi/ThreadCpuTimesDeadlock.java#id1 failed with "OutOfMemoryError: Java heap space"
• 19075b3: 8275788: Create code element with suitable attributes for code snippets
• 7de653e: 8276301: G1: Refine implementation of G1CardSetFreePool::memory_sizes()
• ee49963: 8275534: com.sun.net.httpserver.BasicAuthenticator should check whether "realm" is a quoted string
• 3613ce7: 8275586: Zero: Simplify interpreter initialization
• c62b347: 8276623: JDK-8275650 accidentally pushed "out" file
• ... and 9 more: https://git.openjdk.java.net/jdk/compare/c7f070f5f17dad661cc3296f2e3cd7a1cd5fc742...master

Your commit was automatically rebased without conflicts.

[openjdk]

@pavelrappo Pushed as commit b57715a.

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