ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject AW: incremental compilation
Date Mon, 23 Mar 2009 06:06:19 GMT
It depends on what you think of "incremental compilation".
- differences in the number of files are compiled
- differences inside files are not recognized: the whole file will be recompiled.

But these is not Ant specific - this is based on the underlying compiler, usually the one
from the JDK.
IMHO the Eclipse compiler could work in the 2nd "incremental manner". But I havent tried to
plugin in that compiler into Ant. This should be possible using <javac fork="" executable=""/>.

Patches for extending the compiler list used for 
  <property name="eclipse.home" value="..."/>
  <javac compiler="eclipse"/> 
are welcome ;)


>-----Ursprüngliche Nachricht-----
>Von: news [] Im Auftrag von Sven Köhler
>Gesendet: Samstag, 21. März 2009 14:52
>Betreff: incremental compilation
>according to the docs it seems, that ant is (still) not suitable for 
>incremental compilation. Is that true?
>Quote from the docs of the depend task:
>The most obvious example of these limitations is that the task can't 
>tell which classes to recompile when a constant primitive data type 
>exported by other classes is changed. For example, a change in the 
>definition of something like
>public final class Constants {
>   public final static boolean DEBUG=false;
>will not be picked up by other classes.
>Yes, the good constant-inlining. So there is really nothing 
>to detect that? That is: if I don't do an "ant clean" once in a while, 
>then i will have inconsistent class files?
>I'm rather amazed. But the trouble seems to be, that modern javac 
>doesn't generate any dependency information in addition to or 
>inside the 
>class files. Is that right?
>   Sven
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message