Summary: | [Javadoc] References in Javadoc to deprecated members | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dirk Baeumer <dirk_baeumer> |
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | daniel_megert, hudsonr |
Version: | 3.0 | ||
Target Milestone: | 3.1 M3 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Dirk Baeumer
2004-10-06 07:06:36 EDT
Fixed. New compiler option has been added to address this issue: * COMPILER / Reporting Invalid Javadoc Tags with Deprecated References * Specify whether the compiler will report deprecated references used in Javadoc tags. * <br>Note that this diagnosis can be enabled based on the visibility of the construct associated with the Javadoc; * also see the setting "org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility". * - option id: "org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef" * - possible values: { "enabled", "disabled" } * - default: "enabled" * See also bug 53977. [jdt-core-internal] Test cases added in JavadocTestOptions. *** Bug 71797 has been marked as a duplicate of this bug. *** Maybe there should be a 3rd option (or enabled should work differently). If the method/class containing the JavaDoc is also @deprecated, then it should be able to refer to other @deprecated API without any warnings. And this should be the default setting, as it is with method calls. "Signal the use of deprecated API within deprecated code" is disabled by default. Verified for 3.1M3 with build I20041102 |