Details
-
Bug
-
Resolution: Fixed
-
P3
-
16
-
b32
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8259425 | 17 | Jonathan Gibbons | P3 | Resolved | Fixed | b05 |
JDK-8260110 | 16.0.1 | Jonathan Gibbons | P3 | Resolved | Fixed | b03 |
Description
From Florian Weimer on javadoc-dev:
I'm not sure how recent this change is, but I noticed that "no
comment" warnings are now printed for entities that are related to
serialization: non-public classes which implement Serializable, and
private non-transient fields in serializable classes, and named
private serialization-related methods.
I think it might make sense to add a few words to the warning that
it's about serialization compatibility. It took me a moment to
realize why javadoc was warning about these constructs.
I'm not sure how recent this change is, but I noticed that "no
comment" warnings are now printed for entities that are related to
serialization: non-public classes which implement Serializable, and
private non-transient fields in serializable classes, and named
private serialization-related methods.
I think it might make sense to add a few words to the warning that
it's about serialization compatibility. It took me a moment to
realize why javadoc was warning about these constructs.
Attachments
Issue Links
- backported by
-
JDK-8259425 False positive messages about missing comments for serialization
- Resolved
-
JDK-8260110 False positive messages about missing comments for serialization
- Resolved