Hi,
when working with custom tasks, but also in general,
I frequently find myself doing things like this:
target name=init/
target name=t1 depends=init/
target name=t2 depends=init,t1/
target name=t3 depends=init,t1/
target name=t4 depends=init/
target name=t5 depends
.
In the mean time, you can do:
target name=init/
target name=t1 depends=init/
target name=t2 depends=t1/
target name=t3 depends=t1/
target name=t4 depends=init/
target name=t5 depends=t1,t3/
and depend on the fact t1 depends on init, so any target depending on init
target name=init/
target name=t1 depends=init/
target name=t2 depends=t1/
versus
target name=init/
target name=t1 depends=init/
target name=t2 depends=init,t1/
Is there actually any difference in the way ant will process these
dependencies? They appear
one about relying on gut feel. But that's just me. --DD
-Original Message-
From: Paul Christmann [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 30, 2002 9:27 AM
To: 'Ant Users List'
Subject: Dependency handling (was RE: init target)
target name=init/
target name=t1 depends=init
Paul Christmann wrote:
target name=init/
target name=t1 depends=init/
target name=t2 depends=t1/
versus
target name=init/
target name=t1 depends=init/
target name=t2 depends=init,t1/
Is there actually any difference in the way ant will process
- Original Message -
From: Wilson, Bruce [EMAIL PROTECTED]
by all the tasks in the project. So what's the advantage of putting
definitions like this in an init
target ?
I use my init target to create the file system structure directories.
If a directory is missing, some tasks can
On Wed, 24 Oct 2001 09:19, Wilson, Bruce wrote:
I ask this specifically because right now we're changing our build.xml to
use a path tag to define
the CLASSPATH for compiling our Java code, and we've found that the path
tag can't be in a target
tag - seems it has to be in the project tag.
Wilson, Bruce wrote:
I've seen many example Ant build files that define an init target to
define common properties within;
At one stage (what is now known as version 0.3.1 - before the first
official Ant release) Ant required such a construction to initialise
properties which were
I've seen many example Ant build files that define an init target to
define common properties within;
yet I'm finding that properties defined directly in the project (outside of
any target) are also found
by all the tasks in the project. So what's the advantage of putting
definitions like
