Community
Participate
Working Groups
If I build or rebuild my project, there is one error reported. If I edit a single source file and save it, I see errors reported for this file. If I then do a build or rebuild, the errors disappear again.
I have a single error "This compilation unit indirectly references the missing type XXX". This type of error seems to prevent compilation from doing anything. Even though the one file should not be compiled due to the error, all my files are not compiled.
This error is pretty fatal to the compiler, causing it to abort a build task. It occurs when some binaries are referring to missing ones (in your case one of the involved binary is referencing TraceListener which isn't on your classpath). Given the compiler is blaming source units, it issues this error on the source unit which indirectly referenced the missing type, and then aborts the build given it usually indicates a bogus classpath, and it is pointless to go any further in general. If you fix this very problem, then the build process should fly again.
So what is the preferred way to fix this issue. If I am dependent on another piece of code, I cannot compile my code until I receive some external fix. Currently, there is no way to "not" compile a piece of source. My work around has been to rename problematic files.
There is no way we can build against inconsistent libraries, doing better would hard. Now chances is that the library is fine, but you are missing some of its prerequisites on your classpath. So a classpath change is likely all you need to do. If the library should be ignored until you get a better one, simply remove it from your classpath, if you can, if not then you have to patch to make it consistent...
Ok to close ?
You may close this. I don't like the behavior but I have a workaround.
Closing
