8347123: Add missing @serial tags to other modules#22980
8347123: Add missing @serial tags to other modules#22980hns wants to merge 2 commits intoopenjdk:masterfrom
Conversation
|
👋 Welcome back hannesw! A progress list of the required criteria for merging this PR into |
|
@hns 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 527 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 |
|
@hns 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. |
Webrevs
|
| @@ -1286,6 +1286,9 @@ public boolean isFlavorTextType() { | |||
|
|
|||
| /** | |||
| * Serializes this {@code DataFlavor}. | |||
There was a problem hiding this comment.
This most definitely changes the serialisation spec. So a CSR is needed.
Also shouldn't readExternal be updated to correspond ?
There was a problem hiding this comment.
Only the writeExternal method is required to have a @serialData tag in order to keep javadoc running with -serialwarn option from complaining. I guess the thinking is that the readExternal logic can be derived from that.
@prrace do you have any suggestions for the spec change, or are you ok with the proposed wording?
There was a problem hiding this comment.
There's not a great number of "good" examples of this in the JDK, so probably OK except it
seems like most cases will do it like a normal javadoc method so you'd want an @param tag too.
note : this is a desktop class, so I'm looking at this one but someone else will need to look at all the others
There was a problem hiding this comment.
I've created a CSR with a slightly modified version of the text proposed in this PR:
https://bugs.openjdk.org/browse/JDK-8348408
Other doc tags such as @param and @throws are inherited from the overridden method. Also, this is the only change in this PR that modifies the serialization spec.
There was a problem hiding this comment.
CSR was approved, and I updated the PR with the slightly modified spec text from the CSR.
|
/csr |
|
@prrace has indicated that a compatibility and specification (CSR) request is needed for this pull request. @hns please create a CSR request for issue JDK-8347123 with the correct fix version. This pull request cannot be integrated until the CSR request is approved. |
prrace
left a comment
There was a problem hiding this comment.
Approving the datatransfer portion
|
/reviewers 2 reviewer .. at least ... |
nizarbenalla
left a comment
There was a problem hiding this comment.
Code changes make sense and the updated text matches the text from the CSR.
AlanBateman
left a comment
There was a problem hiding this comment.
I think this is oky, the CSR for the change writeExternal has already been reviewed.
|
/integrate |
|
Going to push as commit 3f0c137.
Your commit was automatically rebased without conflicts. |
Please review a doc-only change to mostly add missing
@serialjavadoc tags. This is a sub-task of JDK-8286931 to allow us to re-enable the javadoc-serialwarnoption in the JDK doc build, which has been disabled since JDK 19.For private and package-private serialized fields that already have a doc comment, the main description is converted to a block tag by prepending
@serialsince these fields do not require a main description. For protected and public serialized fields that require a main description, an empty@serialblock tag is appended to the doc comment instead. The effect is the same, as the main description is used inserial-form.htmlif the@serialtag is missing or empty. For those fields that do not have a doc comment, a doc comment with an empty@serialtag is added.Apart from missing
@serialtags, this PR also adds a@serialDatatag tojava.awt.datatransfer.DataFlavor.writeExternal(ObjectOutput)that the javadoc-serialwarnoption complains about. This is the only change in this PR that adds documentation text and causes a change in the generated documentation.Progress
Issues
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22980/head:pull/22980$ git checkout pull/22980Update a local copy of the PR:
$ git checkout pull/22980$ git pull https://git.openjdk.org/jdk.git pull/22980/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22980View PR using the GUI difftool:
$ git pr show -t 22980Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22980.diff
Using Webrev
Link to Webrev Comment