RE: [Ant-contrib-developers] No link

[Curt A. <ca...@ho...>]

Specifying dependencyDepth will intentionally always cause the task to =
fail.  Basically, it says to truncate dependency checking at a specific =
nesting depth.  The idea is that for very large projects, you would like =
to compile the files most likely to fail first, instead of compiling all =
sorts of files that include the changed header remotely and a couple =
hours latter figure out that you dorked something in the only .cpp file =
that you changed.

I expect to eliminating dependencyDepth by compiling the files sorted by =
the lastest modification of the file and any immediately included =
headers starting with the most recent modifications.

If the build was not failed when you set dependencyDepth, there would be =
the possibility that the product was not consistent with the source file =
set.

p.s. For the people on the list getting tired of my lame excuses about =
trying to get a release out "next weekend" (same story for a couple of =
months now).  I did spend a couple of hours trying to get the Ant xdocs =
stuff working on cpptasks last weekend.  However, I kept getting an =
InvocationTargetException in XDoclet and ran out of time before I could =
get the XDoclet source and track down the problem.