Community
Participate
Working Groups
When defining a typesafe enum, in java 1.5, Eclipse reports missing javadoc comments for each element. This applies even if there is a javadoc comment. The use of the quickfix adds a new javadoc comment, but the warning stays... For example: /** * Test for enumerations */ public enum Test { /** * Comment for <code>abc</code> */ abc, /** * Comment for <code>def</code> */ def; } Reports two warnings: Severity Description Resource In Folder Location Creation Time 1 Javadoc: Missing comment for public declaration Test.java Irrlicht4Java line 9 6 novembre 2004 16:47:49 1 Javadoc: Missing comment for public declaration Test.java Irrlicht4Java line 13 6 novembre 2004 16:47:49 Laurent.
Please do not set target milestone! This target is set by developpers to indicate in which milestone the bug will be fixed. If you want to let us know in which build it occurs (which is a really good think for us...), just put its id when you open the bug. You'll find it in "About Eclipse Platform" dialog. For example, 3.1 M3 is: Version: 3.1.0 Build id: 200411050810
Parsed javadoc is not stored for enum constants...
Fixed. Now compiler does no longer display wrong warnings in enums... [jdt-core-internal] Changes done in Parser#consumeEnumConstantHeaderName(). Test cases added in EnumTests: test033 -> test044
*** Bug 78809 has been marked as a duplicate of this bug. ***
*** Bug 80821 has been marked as a duplicate of this bug. ***
Verified in 200412140800