Bug 77510 - [javadoc] compiler wrongly report deprecation when option "process javadoc comments" is not set
Summary: [javadoc] compiler wrongly report deprecation when option "process javadoc co...
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:
Depends on:
Blocks:
 
Reported: 2004-11-02 13:45 EST by Frederic Fusier CLA
Modified: 2004-12-14 11:37 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frederic Fusier CLA 2004-11-02 13:45:57 EST 
Using v_518.

Compiler reports deprecation warnings when option "Process Javadoc Comments" is
not set for following test case although it should not:
public class X {
	/** 
	* \u000a @deprecated */
	static int x1;
}
Comment 1 Frederic Fusier CLA 2004-11-09 05:59:06 EST 
Fixed.

The example given in comment 0 is incorrect. In this case, compiler should
report the deprecation (character \u000a is a space character).
However, compiler should not report deprecation in following cases:
public class A {
	/** \u000b @deprecated */
	static int i000b;
	/** \u001c @deprecated */
	static int i001c;
	/** \u001d @deprecated */
	static int i001d;
	/** \u001e @deprecated */
	static int i001e;
	/** \u001f @deprecated */
	static int i001f;
	/** \u2007 @deprecated */
	static int i2007;
	/** \u202f @deprecated */
	static int i202f;
}
... and it does not with the fix.

[jdt-core-internal]
Changes done in JavadocParser#checkDeprecation(int,int).

Test cases added in JavadocTestMixed
Comment 2 Olivier Thomann CLA 2004-12-14 11:37:23 EST 
Verified in 200412140800