Question

Recently I started to use Eclipse’s java compiler, because it is significantly faster than standard javac. I was told that it’s faster because it performs incremental compiling. But I’m still a bit unsure about this since I can’t find any authoritative documentation about both – eclispse’s and sun’s – compilers “incremental feature”. Is it true that Sun’s compiler always compiles every source file and Eclipse’s compiler compile only changed files and those that are affected by such a change?

Edit: I’m not using Eclipse autobuild feature but instead I’m setting

-Dbuild.compiler=org.eclipse.jdt.core.JDTCompilerAdapter

for my ant builds.

Answer 1

Is it true that Sun’s compiler always compiles every source file and Eclipse’s compiler compile only changed files and those that are affected by such a change?

I believe that you are correct on both counts.

You can of course force Eclipse to recompile everything.

But the other part of the equation is that Java build tools like Ant and Maven are capable of only compiling classes that have changed, and their tree of dependent classes.

EDIT

In Ant, incremental compilation can be done in two ways:

• By default the <javac> task compares the timestamps of .java and corresponding .class files, and only tells the Java compiler to recompile source (.java) files that are newer than their corresponding target (.class) files, or that don’t have a target file at all.

• The <depend> task also takes into account dependencies between classes, which it determines by reading and analysing the dependency information embedded in the .class files. Having determined which .class files are out of date, the <depend> task deletes them so a following <javac> task will recompile them. However, this is not entirely fool-proof. For example, extensive changes to the source code can lead to the <depend> task may be analysing stale dependencies. Also certain kinds of dependency (e.g. on static constants) are not apparent in the .class file format.

  To understand why Ant <depend> is not fool-proof, read the “Limitations” section of the documentation.