JEP 211: Elide Deprecation Warnings on Import Statements

Joe Darcy joe.darcy at
Thu Oct 16 16:27:42 UTC 2014

On 10/16/2014 1:44 AM, Florian Weimer wrote:
> On 10/16/2014 02:32 AM, mark.reinhold at wrote:
>> New JEP Candidate:
> Would it make sense to suppress then warning on an import statement 
> only if (a) there are uses of this import statement and (b) all these 
> uses are annotated with @Deprecated?
> Or is this too complicated and we should rely on the existing 
> unused-import warning?

I believe relying on existing unused imports warnings is sufficient in 
this case.



More information about the compiler-dev mailing list