-
Notifications
You must be signed in to change notification settings - Fork 6k
8354447: Missing test for retroactive @SuppressWarnings("dangling-doc-comments") behavior #24600
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
Conversation
👋 Welcome back acobbs! A progress list of the required criteria for merging this PR into |
@archiecobbs 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 1085 new commits pushed to the
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 |
@archiecobbs The following label will be automatically applied to this pull request:
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. |
@archiecobbs This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a |
/touch |
@archiecobbs The pull request is being re-evaluated and the inactivity timeout has been reset. |
@archiecobbs This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a |
/touch |
@archiecobbs The pull request is being re-evaluated and the inactivity timeout has been reset. |
Now that JDK 25 has been split off, are there any reviewers available to review this simple change? Thanks in advance. |
/touch |
@archiecobbs The pull request is being re-evaluated and the inactivity timeout has been reset. |
…t a dependency.
Thanks for the review! |
/integrate |
Going to push as commit 0e725c6.
Your commit was automatically rebased without conflicts. |
@archiecobbs Pushed as commit 0e725c6. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This PR adds a regression test for the "retroactive" behavior of
@SuppressWarnings("dangling-doc-comments")
, that is, the warning suppression applies to comments preceding the declaration that the annotation annotates, even though those comments are not within the lexical scope of that declaration. Previously there was no test for this behavior.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24600/head:pull/24600
$ git checkout pull/24600
Update a local copy of the PR:
$ git checkout pull/24600
$ git pull https://git.openjdk.org/jdk.git pull/24600/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24600
View PR using the GUI difftool:
$ git pr show -t 24600
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24600.diff
Using Webrev
Link to Webrev Comment