- Rainer Noack wrote:
> just a hint:
> what's about 's if/unless attributes...
Both and certainly have their uses.
And I don't hesitate to use them where it makes sense to do so. But I
haven't found that they really help much with managing dependencies or
other "tricky" aspects of our buil
7;. Has anyone ever suggested some
mechanism to enable this? Perhaps a command-line option for Ant, or an
attribute to (and maybe as well)?
As things are, any use of causes additional calls to dependent
targets which usually don't need to be executed again.
- Conor MacNeill wrote:
Mich
I've been trying for a very long time now (many man-days) to create Ant
build scripts to handle our new corporate project.
I've been using Ant for over 3 years, and programming professionally for
over 25 years.
Despite all that, I cannot seem to get Ant to do what we need on this
project. I am b
This doesn't seem right to me.
The "Using Ant" chapter of the "Ant User Manual" has always seemed
pretty clear on the subject:
"In a chain of dependencies stretching back from
a given target [...] each target gets executed
only once, even when more than one target
depends on it."
