Community
Participate
Working Groups
See bug #86769. There is no option to specify if enum values should count as public declarations; Right now all enumeration values in an enum are considered public fields and hence always generate a warning/error if the 'Missing javadoc comments' option is set to cause warnings or errors. I'd like to see a new checkbox under 'Missing Javadoc comments': 'Consider enum values'. If turned off, all values within an enum are not flagged as requiring a javadoc comment. Regardless of this feature, enums suffer the same bug as listed in #86769. Tested in 3.1M5.
As said in bug 86769, good idea but only if time permit for 3.1.
API freeze will be on 3.1 M6. Unfortunately we will not have time to fix this until this dead line => defer to next release
Since it's been a few years since this bug has been addressed, I'd ask that it be reevaluated (and thus de-resolved).
Reopen as LATER is deprecated...
Created attachment 77165 [details] patch + test case (also fixes b86769)
*** This bug has been marked as a duplicate of bug 86769 ***