Bug 124697

Description Willian Mitsuda 2006-01-20 13:53:50 EST

Consider the following sample code:

------
DeprecatedClass.java:

package com.mycompany;

@Deprecated
public class DeprecatedClass {
...
}

------
MyClass.java:

package com.mycompany.myapp;

import com.mycompany.DeprecatedClass;

public class MyClass {
    public static void main(String[] args) {
        DeprecatedClass c = new DeprecatedClass();
        ....
    }
}

------

In MyClass.java, the Eclipse compiler warns about DeprecatedClass being, er, deprecated ;-)

Suppose I want intentionally to use DeprecatedClass, because it is legacy code and I don't have a drop-in replacement solution, but I don't want the deprecation warning in this method (or class), so I annotate it with @SuppressWarnings:

package com.mycompany.myapp;

import com.mycompany.DeprecatedClass;

public class MyClass {
    @SuppressWarnings("deprecation")
    public static void main(String[] args) {
        DeprecatedClass c = new DeprecatedClass();
        ....
    }
}

and the warning disappears from main method, but it still remains in the import clause!

Yes, I know that @SupressWarnings is not applicable to import statements, but I think the compiler should not warn a deprecated class in the import statement if the code block where it is used is annotated with @SuppressWarnings("deprecation")