-
Bug
-
Resolution: Fixed
-
P4
-
9
-
b42
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8085278 | emb-9 | Jan Lahoda | P4 | Resolved | Fixed | team |
During efforts to rid the JDK code base of lint warnings, it has been observed that the deprecation lint warnings currently issued on import statements are a nuisance and often uninformative.
While use of deprecated types within methods or in method signatures can be suppressed using @SuppressWarning, and annotation *cannot* be used to suppress the deprecation warning on an import. To get a warning-free program that must use deprecated types or method, it is unreasonable to impose a requirement that all references to the deprecated elements must be through a fully qualified name.
Therefore, it would be helpful if the JLS were changed to no longer require a deprecation warning be used for import statements.
While use of deprecated types within methods or in method signatures can be suppressed using @SuppressWarning, and annotation *cannot* be used to suppress the deprecation warning on an import. To get a warning-free program that must use deprecated types or method, it is unreasonable to impose a requirement that all references to the deprecated elements must be through a fully qualified name.
Therefore, it would be helpful if the JLS were changed to no longer require a deprecation warning be used for import statements.
- backported by
-
JDK-8085278 Don't issue deprecation warnings on import statements
-
- Resolved
-
- csr of
-
CCC-8032211 Don't issue deprecation warnings on import statements
-
- Closed
-
- relates to
-
JDK-6598104 javac should not warn about imports of deprecated classes
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
JDK-8042566 JEP 211: Elide Deprecation Warnings on Import Statements
-
- Closed
-
(1 relates to)