-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8346667: Doccheck: warning about missing </span> before <h2> #22833
Conversation
👋 Welcome back nbenalla! A progress list of the required criteria for merging this PR into |
@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:
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 3 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
@nizarbenalla To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command. Applicable Labels
|
…ame look" This reverts commit c86a3e5.
/label add core-libs |
@nizarbenalla |
Webrevs
|
I suggest you try and move this section immediately above the |
Done, thanks for the suggestion. The problem seems to have gone away. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Looks good.
Thanks for the review Paul. /integrate |
Going to push as commit 054c644.
Your commit was automatically rebased without conflicts. |
@nizarbenalla Pushed as commit 054c644. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport jdk jdk24 |
@nizarbenalla the backport was successfully created on the branch backport-nizarbenalla-054c644e-jdk24 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk24, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk:
|
Please review this doc-only patch to avoid some unwanted failures in our HTML checks.
Javadoc wraps everything under
@param
in a<span>
, so having anh2
tag there trips some of our tests that use html validators (html-tidy and some other tests). I believe you shouldn't have an<h2>
inside of a span.This patch moves the text about "Value-based classes and identity operations" above the
@param
tag, it will now be rendered at the bottom of the class documentation.This will need to be backported to JDK 24.
TIA.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22833/head:pull/22833
$ git checkout pull/22833
Update a local copy of the PR:
$ git checkout pull/22833
$ git pull https://git.openjdk.org/jdk.git pull/22833/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22833
View PR using the GUI difftool:
$ git pr show -t 22833
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22833.diff
Using Webrev
Link to Webrev Comment