-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8264779: Fix doclint warnings in java/nio #3376
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 ccleary! A progress list of the required criteria for merging this PR into |
/csr |
@c-cleary has indicated that a compatibility and specification (CSR) request is needed for this pull request. |
Webrevs
|
/label add nio |
@AlanBateman |
@@ -39,7 +39,15 @@ | |||
@java.io.Serial | |||
static final long serialVersionUID = 4355821422286746137L; | |||
|
|||
/** | |||
* The invalid input path string. | |||
*/ |
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 should probably be "The input string" to be consistent with the getInput method.
@@ -40,6 +40,9 @@ | |||
@java.io.Serial | |||
static final long serialVersionUID = -5369283889045833024L; | |||
|
|||
/** | |||
* The name of the {@code UserPrincipal} that does not exist. |
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.
Probably best to use "user principal name" so that it is consistent with getName.
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 Alan, will update as you suggest shortly with respect to both of your comments (also thanks for adding the nio label!)
@@ -41,6 +41,9 @@ | |||
@java.io.Serial | |||
private static final long serialVersionUID = -3438823399834806194L; | |||
|
|||
/** | |||
* The length of the input byte sequence. |
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.
Should this comment also refer to the character sequence?
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.
It could, maybe something like "The length of the input byte (or character) sequence." would work?
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.
or just "The length of the input" so that it is consistent with the description of the getInputLength method.
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.
That sounds good.
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.
Changed to "The length of the input." in the most recent commit.
@c-cleary 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 41 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 (@ChrisHegarty, @irisclark, @AlanBateman, @naotoj) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
/sponsor |
@ChrisHegarty @c-cleary Since your change was applied there have been 41 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit a45733f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This fix addresses the following warnings which were generated by building JDK API documentation with the
-Xdoclint:all
option enabled:Changes to
genExceptions.sh
and the twoexceptions
templates are to address the warnings concerned withUnsupportedCharsetException.java
andIllegalCharsetNameException.java
which are generated whenmake jdk-image
is run.CSR: https://bugs.openjdk.java.net/browse/JDK-8264844
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3376/head:pull/3376
$ git checkout pull/3376
Update a local copy of the PR:
$ git checkout pull/3376
$ git pull https://git.openjdk.java.net/jdk pull/3376/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3376
View PR using the GUI difftool:
$ git pr show -t 3376
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3376.diff