Summary: | [javadoc] "Only consider members as visible as" is does not work for syntax error | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | David Audel <david_audel> |
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.1 | ||
Target Milestone: | 3.1 M4 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
David Audel
2004-11-03 07:42:06 EST
Fixed. All warnings concerning tags are now reported according to visibility level. Here are warning which will take into account visibility level after the fix although they did not before: - "Only static field reference is allowed for @value tag" - "Missing parameter name" - "Missing reference" - "Missing class name" However, compiler will continue to report syntax error in Javadoc comments whatever the visibility level set by user. So, following warnings will continue to be signaled whatever the visibility level: - Unexpected tag - Duplicate tag for return type - Invalid class name - Invalid reference - Malformed reference (missing end space separator) - Malformed link reference - Invalid parameters declaration - Invalid tag - Missing closing brace for inline tag - Missing #: "{0}" - Missing return type description - Unexpected text Perhaps UI is ambiguous and should put a specific text for visibility? [jtd-core-internal] Changes made in: - Javadoc#resolveReference(Expression, Scope) - AbstractCommentParser: #parseParam(), #parseReference(), parseThrows() - ProblemReporter: #javadocInvalidValueReference(...), #javadocMissingParamName(...) #javadocMissingReference(...), #javadocMissingThrowsClassName(...) #javadocVisibility(int, int) Test cases added in JavadocTestMixed Verified in 200412140800 |