To avoid the warning:
do not import the class
instead use the fully qualified class name
and use it in as few locations as possible.
More Related Contents:
- Type mismatch: cannot convert from Inventory to JPanel
- Why is Java Vector (and Stack) class considered obsolete or deprecated?
- Why is using a wild card with a Java import statement bad?
- Replacements for deprecated JPMS modules with Java EE APIs
- What is SuppressWarnings (“unchecked”) in Java?
- Is it wrong to use Deprecated methods or classes in Java?
- What’s the syntax to import a class in a default package in Java? [duplicate]
- What is the list of valid @SuppressWarnings warning names in Java?
- Eclipse error: “The import XXX cannot be resolved”
- Why were applets deprecated in JDK 9?
- Is the buildSessionFactory() Configuration method deprecated in Hibernate?
- Java: Why is the Date constructor deprecated, and what do I use instead?
- Change Name of Import in Java, or import two classes with the same name
- Help with packages in java – import does not work
- Deprecated ManagedQuery() issue
- Why were most java.util.Date methods deprecated?
- Find out which classes of a given API are used
- Class is a raw type. References to generic type Class should be parameterized
- Why is my OBJ parser rendering meshes like this?
- Performance difference between a wild card import and the required class import
- Java: import statement vs fully qualified name?
- Java Package Does Not Exist Error
- java.net.URLEncoder.encode(String) is deprecated, what should I use instead?
- Importing JSON into an Eclipse project
- Why is the Date constructor deprecated, and what do I use instead?
- Android – onRequestPermissionsResult() is deprecated. Are there any alternatives?
- why autoimport only java.lang package?
- org.hibernate.annotations.Entity deprecated in Hibernate 4?
- How to suppress Java compiler warnings for specific functions
- Java error – bad source file: file does not contain class x . Please remove or make sure it appears