Community
Participate
Working Groups
Build 20040506 When some binary file references a non defined type, the compilation process is terminated, with an indication that there was an indirect reference from binaries. The problem is that there is no mention of the original portion of source which triggered to load these inconsistent binaries. Highlighting the offending source would improve lisibility of these errors. There are cases where the classpath is simply broken, but it could just be that someone did accidentally expose some internal code through an API. In case the latter is true, it is really hard to figure the offending reference from sources.
Added support to catch AbortCompilation in some entry point of name resolution which are aware of an invocation site or an ASTNode. Then use their source positions to position the problem associated to the AbortCompilation exception. Fixed
We know return an error like this: Severity Description Resource In Folder Location Creation Time 2 The type plugin3.SecretClass cannot be resolved. It is indirectly referenced from required .class files. Main.java plugin1/src/plugin1 line 20 18 mai 2004 14:51:29 The error is located on the right part of the code and not on the compilation unit. Verified in 200405180816
*** Bug 11218 has been marked as a duplicate of this bug. ***
