Bug 78018 - [1.5][javadoc] Missing Javadoc comments Problem for enums
Summary: [1.5][javadoc] Missing Javadoc comments Problem for enums
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M4   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 78809 80821 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-11-06 11:03 EST by Laurent JEANPIERRE CLA
Modified: 2004-12-14 11:41 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Laurent JEANPIERRE CLA 2004-11-06 11:03:12 EST
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.
Comment 1 Frederic Fusier CLA 2004-11-09 04:56:35 EST
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
Comment 2 Frederic Fusier CLA 2004-11-09 12:52:59 EST
Parsed javadoc is not stored for enum constants...
Comment 3 Frederic Fusier CLA 2004-11-09 21:00:26 EST
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
Comment 4 Neal Sanche CLA 2004-11-16 22:32:29 EST
*** Bug 78809 has been marked as a duplicate of this bug. ***
Comment 5 Frederic Fusier CLA 2004-12-13 13:41:13 EST
*** Bug 80821 has been marked as a duplicate of this bug. ***
Comment 6 Olivier Thomann CLA 2004-12-14 11:41:03 EST
Verified in 200412140800