Community
Participate
Working Groups
I got a java compilation error due to an incomplete build path (basically some jar file I download had some missing class files). I tried to set the compiler's "incomplete build path" option from "error" to "warning" to avoid the build failure, but it still gave me the same error. When I tried to build the code using javac, the javac compiler can successfully ignored this problem (since I am not actually referencing the missing class file). It seems the IDE doesn't really turn the option from "error" to "warning".
Our option wording is likely a bit confusing. When telling the compiler to treat incomplete build path as a warning, it does allow compiling even if some entries on the classpath are unbound. This doesn't affect the fact that subsequent unresolvable references in the source will be reported as errors; it is only a pre-sanity check. Now it is true that our compiler eagerly needs more indirect references from binaries than other compilers. We have improved our behavior since R2.1, and a patch is posted on JDT/Core 2.2 update area: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core- home/r2.2/main.html#updates
Closing as duplicate. Please reopen if symptoms persist with the patch. *** This bug has been marked as a duplicate of 21661 ***
