"intermediate directory contains no translation units" error while Coverity Static Analysis of my Java project

java static-analysis coverity
user3604158 picture user3604158 · May 12, 2016 · Viewed 7.8k times · Source

Recieved following warning while capturing the build for my project on Coverity. [WARNING] No files were emitted. This may be due to a problem with your configuration or because no files were actually compiled by your build command. Please make sure you have configured the compilers actually used in the compilation.

Answer

Caleb picture Caleb · May 20, 2016

cov-build needs to know about what compilers you have in your build system. This is informed by the generated configs (using cov-configure).

For a Java project, usually cov-configure --java is sufficient. This will have cov-build look for javac invocations.

Another common problem is that you didn't do a clean build, so no actual compilations were seen.

If you've configured Java properly and captured a clean build and still aren't seeing TUs emitted, then you'll need to inspect the build log (underneath <intermediate directory>/build-log.txt). This should give some indication of what's gone wrong.

Related questions

javax.annotation: @Nullable vs @CheckForNull

What is the difference between the two? Both seem to mean that the value may be null and should be dealt with accordingly i.e. checked for null. Update: The two annotations above are part of JSR-305/FindBugs: http://findbugs.…

Read More
Checkstyle vs. PMD

We are introducing static analysis tools into the build system for our Java product. We are using Maven2 so Checkstyle and PMD integration come for free. However it looks like there is a large overlap in functionality between these two …

Read More
Static Analysis tool recommendation for Java?

Being vaguely familiar with the Java world I was googling for a static analysis tool that would also was intelligent enough to fix the issues it finds. I ran at CodePro tool but, again, I'm new to the Java community …

Read More