JDK-8305004: add @spec tags to langtools modules

[jonathan-gibbons]

Please review a simple doc-only PR to add @spec tags to 3 "langtools" modules, for eventual use in an "External Specifications" page.

---

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-8305004: add @SPEC tags to langtools modules

Reviewers

• Iris Clark (@irisclark - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 13201

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/13201.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 labels will be automatically applied to this pull request:

• compiler
• javadoc

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

[mlbridge]

Webrevs

• 00: Full (349423d0)

[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:

8305004: add @spec tags to langtools modules

Reviewed-by: iris

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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.

[jonathan-gibbons]

/integrate

[openjdk]

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

• 32ef452: 8304884: Update Bytecodes data to be mostly compile time constants
• 927e674: 8300977: Retire java.io.ExpiringCache
• c90699e: 8304989: unnecessary dash in @param gives double-dash in docs
• 395a4ce: 8304591: (fs) UnixPath.stringValue need not be volatile
• 60640a2: 8300979: Lazily initialize (byte, char)arr in java.io.DataInputStream
• cddaf68: 8304962: sun/net/www/http/KeepAliveCache/B5045306.java: java.lang.RuntimeException: Failed: Initial Keep Alive Connection is not being reused
• a06f461: 8303214: Typo in java.util.Collections#synchronizedNavigableMap javadoc
• 7987ad4: 8304412: Serial: Refactor old generation cards update after Full GC
• 3c4cd50: 8304963: HttpServer closes connection after processing HEAD after JDK-7026262
• 4f625c0: 8304543: Modernize debugging jvm args in test/hotspot/jtreg/vmTestbase/nsk/jdi/Argument/value/value004.java
• ... and 1 more: https://git.openjdk.org/jdk/compare/6aec6f3a842ead30b26cd31dc57a2ab268f67875...master

Your commit was automatically rebased without conflicts.

[openjdk]

@jonathan-gibbons Pushed as commit 83ce65e.

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