Community
Participate
Working Groups
Using 0518_0816, some malformed inline javadoc tags are not reported as malformed. For example: @{link #foo())} is not reported as malformed, but the javadoc tool reports it as malformed. Removing the extra closing parenthesis fixes it.
Created attachment 10816 [details] Test case This doesn't report any error even with malformed javadoc comment reported as error.
The javadoc tool reports: c:\eclipse\workspaces\test0518\P\src\p\B.java:8: warning - Tag @link: malformed: "A#bar())" c:\eclipse\workspaces\test0518\P\src\p\B.java:8: warning - Tag @link: malformed: "A#bar())" c:\eclipse\workspaces\test0518\P\src\p\B.java:8: warning - Tag @link: reference not found: A#bar()) c:\eclipse\workspaces\test0518\P\src\p\B.java:8: warning - Tag @link: malformed: "A#bar())" c:\eclipse\workspaces\test0518\P\src\p\B.java:8: warning - Tag @link: malformed: "A#bar())" c:\eclipse\workspaces\test0518\P\src\p\B.java:8: warning - Tag @link: reference not found: A#bar()) c:\eclipse\workspaces\test0518\P\src\p\B.java:8: warning - Tag @link: malformed: "A#bar())"
Removing the extra ) fixes the problem.
Fixed. Now method references with no separation (ie. white space) after the argument declaration closing brace are considered as malformed and warned with following new Javadoc message: Javadoc: Malformed reference (missing separator after method reference closing brace) [jdt-core-internal] Changes done in: 1- AbstractCommentParser.parseArguments(Object): when closing brace is encountered and valid in arguments syntax, then verify that current character is a white space, 2- ProblemReporter, IProblem and message.properties: Add new message Test case added in JavadocTestMixed
Verified in 200405281200