In the "old-fashioned way", are you compiling files using the @file syntax? The reason
I ask is that with javac, deprecation warnings are only issued for files outside of
the current compilation; according to Java bug 4233889 (Would like deprecation
warnings for files in current compilation), the documentation for -deprecation says:
Note: A deprecation warning is suppressed if the compilation
unit containing the deprecation is being compiled at
the same time as the compilation unit using the
deprecated class or member. This allows legacy APIs
to be built without warnings. There currently is no
other way to suppress the deprecation warnings.
There's more information in Java bug 4216683 (Inconvenient javac deprecation warning
suppression).
Kendall
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 23, 2002 16:04
Subject: Missing deprecation warnings
> If I compile files the old-fashioned way (without using Ant) using Sun's Java
> 1.3.1, I get roughly twice as many deprecation warnings as I get with Ant. It
> appears that many of the "missing" deprecation warnings have to do with
> deprecated methods in interfaces. Do you have any idea why those warnings would
> not appear? Or better yet, how can I get them to appear?
