Mike Schilling wrote:
> Arne Vajhøj wrote:
>> Mike Schilling wrote:
>>> Arne Vajhøj wrote:
>>>> Aryeh M. Friedman wrote:
>>>>> I am looking for a class/program that will scan a .java file for
>>>>> im****ts (recursively) to discover which ones need to be rebuilt.
>>>>> This is close to GNU's makedepend or cook's c_incl.
>>>> You don't use that type of tools with Java.
>>>>
>>>> The javac compiler itself compiles missing parts.
>>>>
>>>> And the ant tool (which you should use for build) checks what to
>>>> rebuild based on dates similar to ant.
>>>>
>>>> Just use ant and javac and forget about dependencies.
>>> And when that's not good enough (like when superclass change,
>>> require
>>> subcl***** to recompile too), curse a bit, delete all the .class
>>> files, and rebuild the whole thing.
>> Many people make a clean target in build.xml !
>
> I always do, for several reasons; the above is one of them. My
> comment was a complaint about the fact that the <javac> task is
> *almost* good enough to handle dependencies, but not quite. When I,
> for instance, get a batch of newer source code from the SCM system, I
> always do a clean build, since there's no way to be sure it isn't
> necessary, and I don't want to waste time with spurious problems from
> not building clean when it was required.
And usually Java builds are reasonable fast even when building from
scratch.
Arne
|
