JDK-7101822 causes spurious 'annotation.type.not.applicable' error

Liam Miller-Cushon cushon at google.com
Mon Jul 20 18:29:10 UTC 2015

Thanks Jan,

On Mon, Jul 20, 2015 at 12:27 AM, Jan Lahoda <jan.lahoda at oracle.com> wrote:

> The problem seems to be in an inappropriate handling of the
> CompletionFailure that is triggered due to the missing class. I think it
> needs to be caught and a proper error reported for it.

That sounds good to me. I'm now working around it by catching and reporting
the CompletionFailure in checkImportsUnique.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/compiler-dev/attachments/20150720/13247e1a/attachment.html>

More information about the compiler-dev mailing list