| Summary: | [javadoc] \u200B and \u3000 aren't supported in javadoc | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | David Audel <david_audel> |
| Component: | Core | Assignee: | JDT Core Triaged <jdt-core-triaged> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | CC: | Olivier_Thomann |
| Version: | 3.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
Fix is trivial. Finally it is not that simple. \u3000 seems to be accepted withing doc comment, but it is not accepted inside the normal code. Tagging as 3.8. Time permitting. The two characters are not accepted inside normal code, but they seem to be accepted into javadoc comment. This requires a special handling inside comments. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
build 3.3 1) create these classes package p; public class Test1 {} package p; public class Test2 {} package p; public class Test3 {} 2) create Bug.java package p; public class Bug { /** * @see\u0020Test1 * @see\u200BTest2 * @see\u3000Test3 */ public void foo() {} } 3) Enable diagnosis of malformed javadoc comments There are two problem Javadoc: Missing reference Javadoc: Missing reference The JDT javadoc diagnosis doesn't support \u200B and \u3000 but the javadoc tools support them.