-
Notifications
You must be signed in to change notification settings - Fork 7
8285400: Add '@apiNote' to the APIs defined in Java SE 8 MR 3 #7
Conversation
|
👋 Welcome back poonam! A progress list of the required criteria for merging this PR into |
Webrevs
|
|
How about the SHA512_224 and SHA512_256 constants in java/security/spec/MGF1ParameterSpec.java? Should add the since and apiNot javadoc tags as well? |
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.
Is the word choice confirmed/approved, or still up for editing? Seems like this should be in past tense, IMHO.
This method was added in Java SE 8 Maintenance Release 3.
|
Shouldn't the copyright dates be updated to 2022? These are significant changes to the files involved. |
| * supposed to be used for digital signatures, an | ||
| * {@code InvalidKeyException} is thrown. | ||
| * | ||
| * @apiNote This method is defined in Java SE 8 Maintenance Release 3. |
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.
Hmm, there are other pkg private methods added in the maintenance release which do not have the @since javadoc tag. For consistency sake, maybe removing the @since tag here and no need to add @apiNote then?
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.
I apparently let this slip through, this @since should not have been there. Please remove it and the @apiNote. Thanks.
The |
| * @apiNote | ||
| * This method should be called by TLS server applications before the TLS | ||
| * @apiNote This method is defined in Java SE 8 Maintenance Release 3. | ||
| * |
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.
IMHO, this needs a separator here to separate the existing API from the addition. Or maybe a second @apiNote? It currently renders as this:
API Note:
This method is defined in Java SE 8 Maintenance Release 3. This method
should be called by TLS server application...
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.
I suggest using <p> to start with a new paragraph.
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.
I'm guessing @mlchung meant <p>. Her suggestion didn't render correctly.
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.
Yes, that's what I meant. I updated the formatting of my comment.
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.
FYI: a second @apiNote does not render correctly, suggest using
which I've verified does.
API Note:
This method is defined in Java SE 8 Maintenance Release 3.
This method should be called by TLS server...
| * | ||
| * @apiNote | ||
| * This method should be called by TLS server applications before the TLS | ||
| * @apiNote This method is defined in Java SE 8 Maintenance Release 3. |
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.
Same concern here about either a second @apiNote or a separator.
|
Same concern as @valeriepeng on both the |
|
@bradfordwetmore @valeriepeng I have addressed all the concerns and have updated the PR. Please take a look. |
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.
Copyright date updates not complete.
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 change looks good to me. Thanks for doing this update.
Can you file a JBS issue to fix in the mainline to add back @since in the constants in MGF1ParameterSpec class? Thanks.
Good idea, thanks @mlchung! |
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.
LGTM.
|
@poonamparhar This change now passes all automated pre-integration checks. 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 4 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 |
|
/integrate |
|
Going to push as commit 3740d05.
Your commit was automatically rebased without conflicts. |
|
@poonamparhar Pushed as commit 3740d05. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This change adds "apiNote This method is defined in Java SE 8 Maintenance Release 3." to the doc comments of the new APIs added with the following changesets in Java SE MR3 :
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk8u-ri pull/7/head:pull/7$ git checkout pull/7Update a local copy of the PR:
$ git checkout pull/7$ git pull https://git.openjdk.java.net/jdk8u-ri pull/7/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 7View PR using the GUI difftool:
$ git pr show -t 7Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk8u-ri/pull/7.diff