ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Garcia, Gilles" <>
Subject RE: rebuild when compiler changes ? (was:How to specify the locat ion of the compiler ?)
Date Tue, 13 Feb 2001 22:30:56 GMT
But the compiler options are file-specific, since a .class file
may have been compiled with a different set than its neighbors.
Thus one should compare the compiler configuration for each .class
against the new one.

-----Original Message-----
From: Bill Burton
To: Ant User Mailing List
Sent: 2/13/01 5:22 PM
Subject: Re: rebuild when compiler changes ? (was:How to specify the
location    of the compiler ?)


The default compiler properties file doesn't have to be "lying around,"
but can be checked into the SCM system as should anything for production
builds.  For developer builds, the logical place for a compiler
file might be the target directory for the compile.  

The point I was attempting to make is that without a lot of effort, it
possible to implement at least some level of support for dependency
checking based on compiler options.


"Garcia, Gilles" wrote:
> Usually one does builds on top of a Version control system
> e.g. CVS, RCS, CLearCase, etc ...
> And writing files is not going to be the whole answer. One cannot
> these requirements from the undelying Revision control system.
> When you check out a file, ITS properties file has to be used for
> depend/rebuild decisions, not some properties file which happens to be
> lying around from a previous invocation of Ant.
> It ain't that straightforward.

View raw message