-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8252830: Correct missing javadoc comments in java.rmi module #79
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
8252830: Correct missing javadoc comments in java.rmi module #79
Conversation
👋 Welcome back rriggs! A progress list of the required criteria for merging this PR into |
Add the missing comments where required by javadoc -Xdoclint to document public and serializable classes, methods, and fields. |
@RogerRiggs 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 |
/csr |
@RogerRiggs has indicated that a compatibility and specification (CSR) request is needed for this pull request. |
Webrevs
|
* @param in the {@code ObjectInputStream} from which data is read | ||
* @throws IOException if an I/O error occurs | ||
* @throws ClassNotFoundException if a serialized class cannot be loaded | ||
* | ||
*/ | ||
private void readObject(ObjectInputStream in) |
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.
Hi Roger, you could take this opportunity to add the @Serial
annotation to this method (here and in the other files you modified as well.
@@ -228,6 +228,9 @@ public boolean equals(Object obj) { | |||
* java.rmi.server.RemoteObject RemoteObject} | |||
* <code>writeObject</code> method <b>serialData</b> | |||
* specification. | |||
* | |||
* @param out the {@code ObjectOutputStream} to which data is written | |||
* @throws IOException if an I/O error occurs | |||
**/ | |||
private void writeObject(ObjectOutputStream out) |
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 comment as above...
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.
Hi Roger,
The combined changes to both commits look good
@RogerRiggs This change now passes all automated pre-integration checks. In addition to the automated checks, the change must also fulfill all project specific requirements After integration, the commit message will be:
Since the source branch of this PR was last updated there have been 44 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 automatic rebasing, please merge ➡️ To integrate this PR with the above commit message to the |
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.
Otherwise looks good.
@@ -228,6 +229,9 @@ public boolean equals(Object obj) { | |||
* java.rmi.server.RemoteObject RemoteObject} | |||
* <code>writeObject</code> method <b>serialData</b> | |||
* specification. | |||
* | |||
* @param out the {@code ObjectOutputStream} to which data is written | |||
* @throws IOException if an I/O error occurs | |||
**/ | |||
private void writeObject(ObjectOutputStream out) |
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.
one @Serial
still missing here?
*/ | ||
@java.io.Serial | ||
private void writeObject(java.io.ObjectOutputStream out) | ||
throws java.io.IOException |
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's a little odd to see an import of java.io.IOException (which is used by the @throws
tag) but not to have it used here. There's another occurrence down below. These files have a mixture of imports and fully qualified names, which I find irritating, which might be nice to clean up. But you might find beyond the scope of this change. So, clean up as much of this as you like, or none if you prefer, no big deal.
Hi Stuart,
I'm going to leave this for later, its a bit out of scope and every change
prompts the people who have already reviewed it to need to review it again.
Thanks, Roger
…On 9/8/20 5:38 PM, Stuart Marks wrote:
***@***.**** commented on this pull request.
------------------------------------------------------------------------
In src/java.rmi/share/classes/java/rmi/server/RemoteObject.java
<https://urldefense.com/v3/__https://github.com/openjdk/jdk/pull/79*discussion_r485210638__;Iw!!GqivPVa7Brio!OBTG2nlJMZowBn3gf_R72ZdA_MzJASDpLUuJFDC4fTAxUL_AnJ9Pfvctp470Fa4a$>:
> */
+ @java.io.Serial
private void writeObject(java.io.ObjectOutputStream out)
throws java.io.IOException
It's a little odd to see an import of java.io.IOException (which is
used by the ***@***.***| tag) but not to have it used here. There's
another occurrence down below. These files have a mixture of imports
and fully qualified names, which I find irritating, which might be
nice to clean up. But you might find beyond the scope of this change.
So, clean up as much of this as you like, or none if you prefer, no
big deal.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://urldefense.com/v3/__https://github.com/openjdk/jdk/pull/79*pullrequestreview-484510521__;Iw!!GqivPVa7Brio!OBTG2nlJMZowBn3gf_R72ZdA_MzJASDpLUuJFDC4fTAxUL_AnJ9Pfvctp0HjkJMk$>,
or unsubscribe
<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AAIRSVBO6NWK7WC75GOJRETSE2P67ANCNFSM4RAD5TXQ__;!!GqivPVa7Brio!OBTG2nlJMZowBn3gf_R72ZdA_MzJASDpLUuJFDC4fTAxUL_AnJ9Pfvctp5LhysgN$>.
|
/integrate |
@RogerRiggs Since your change was applied there have been 44 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 418e4a2. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
openjdk#79) This patch update return_phi of AllocationState in Parse::do_exits(). (6107 Phi) = (6103 region, 3789 CheckCastPP, 3789 CheckCastPP) will become (3789 CheckCastPP) after first _gvn.transform(). If we still use 6107 Phi, we will have problem in process_phi later. Co-authored-by: Xin Liu <xxinliu@amazon.com>
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/79/head:pull/79
$ git checkout pull/79