I'm checking this in. I was getting a fair number of warnings for javadoc references to non-visible or deprecated members. The latter seemed reasonable to allow in our code; the former, well, maybe. I'm enabling both, and we can see how it goes.
Tom 2005-09-13 Tom Tromey <[EMAIL PROTECTED]> * .settings/org.eclipse.jdt.core.prefs: Ignore javadoc warnings for hidden or deprecated members. Index: .settings/org.eclipse.jdt.core.prefs =================================================================== RCS file: /cvsroot/classpath/classpath/.settings/org.eclipse.jdt.core.prefs,v retrieving revision 1.4 diff -u -r1.4 org.eclipse.jdt.core.prefs --- .settings/org.eclipse.jdt.core.prefs 13 Sep 2005 03:24:24 -0000 1.4 +++ .settings/org.eclipse.jdt.core.prefs 14 Sep 2005 01:02:59 -0000 @@ -1,4 +1,4 @@ -#Mon Sep 12 20:53:44 MDT 2005 +#Tue Sep 13 16:15:04 MDT 2005 eclipse.preferences.version=1 org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.4 @@ -25,8 +25,8 @@ org.eclipse.jdt.core.compiler.problem.indirectStaticAccess=ignore org.eclipse.jdt.core.compiler.problem.invalidJavadoc=warning org.eclipse.jdt.core.compiler.problem.invalidJavadocTags=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef=enabled +org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef=disabled +org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef=disabled org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility=private org.eclipse.jdt.core.compiler.problem.localVariableHiding=ignore org.eclipse.jdt.core.compiler.problem.methodWithConstructorName=warning _______________________________________________ Classpath-patches mailing list Classpath-patches@gnu.org http://lists.gnu.org/mailman/listinfo/classpath-patches