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
On 8/4/20 11:20 AM, Florian Weimer wrote:
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, a
On 8/4/20 12:18 PM, Florian Weimer wrote:
* Jonathan Gibbons:
On 8/4/20 11:20 AM, Florian Weimer wrote:
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 Serializ
* Jonathan Gibbons:
> On 8/4/20 11:20 AM, Florian Weimer wrote:
>> 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 fi
* Jonathan Gibbons:
> It would be surprising (bug?) to see a warning being generated for a
> class that
> is not being documented. I assume you have not given command-line options
> to include that class in the documentation. I'm also guessing that this is
> while using javadoc, where the recen
