The current name binding rules only consider names in Jasmin files. However, you could refer to names in a class file without a corresponding Jasmin version. This is typically the case for all library classes. A naive solution would be to convert those class files into Jasmin. But this would require more analysis work, since this would also analyse method bodies.

A better solution would only analyse class, method and field names of class files. You should come up with a way to feed the index with such information. The challenge here is to wrap this in a task and to only analyse class files, when needed. For the analysis itself, you can probably rely on the same framework as for class file generation.

Submitted by Guido Wachsmuth on 5 March 2014 at 13:51