-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
JDK-8276674 : Malformed Javadoc inline tags in JDK source #6443
Conversation
Hi @tprinzing, welcome to this OpenJDK project and thanks for contributing! We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user tprinzing" as summary for the issue. If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing |
@tprinzing The following labels 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 lists. If you would like to change these labels, use the /label pull request command. |
/covered |
Thank you! Please allow for a few business days to verify that your employer has signed the OCA. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated! |
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.
Remarkable to have not been noticed for so long!
@tprinzing 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 26 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@jonathan-gibbons, @RogerRiggs, @pavelrappo, @bchristi-git) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Remarkable, but not too surprising: the PR consists of source files and tests that are not part of the API Documentation. |
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.
Looks good.
* If the AST node appears in the same line number as the main diagnostic, the line is information is omitted. | ||
* Otherwise both line and column information is included, using the format @{code line:col}". | ||
* Otherwise both line and column information is included, using the format {@code line:col}". |
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.
Not a showstopper by any means. But while you are at it, maybe you could also fix this?
* If the AST node appears in the same line number as the main diagnostic, the line is information is omitted. | |
* Otherwise both line and column information is included, using the format @{code line:col}". | |
* Otherwise both line and column information is included, using the format {@code line:col}". | |
* If the AST node appears in the same line number as the main diagnostic, the line information is omitted. | |
* Otherwise both line and column information is included, using the format {@code line:col}. |
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.
This part was recently integrated in #6602. I assume there will be a trivial merge conflict to resolve.
Given that this PR affects files that aren't rooted under java/util/stream, I would either rename the PR or exclude the unrelated files. If this PR is going to sit there for some more time, I would prefer the latter. This is because the PR has already conflicted with a few other issues related to malformed javadoc tags (e.g. JDK-8276683 and JDK-8276684). So either rename and integrate soon, or exclude the unrelated files. |
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.
Looks good. Thanks for renaming, per Pavel's suggestion. I can sponsor this.
/integrate |
@tprinzing |
/sponsor |
Going to push as commit 652b5f8.
Your commit was automatically rebased without conflicts. |
@bchristi-git @tprinzing Pushed as commit 652b5f8. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6443/head:pull/6443
$ git checkout pull/6443
Update a local copy of the PR:
$ git checkout pull/6443
$ git pull https://git.openjdk.java.net/jdk pull/6443/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6443
View PR using the GUI difftool:
$ git pr show -t 6443
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6443.diff