>
>
> 5. I don't want every build.xml file to contain hard-coded references to the
> infrastructure - for example:
>
>
>
>
Look at the proprty task, you can pull in property values from a file.
>From the docs:
When a property was set by the user, or was a property in a parent project (that
s
On Fri, 20 Apr 2001 [EMAIL PROTECTED] wrote:
> We use ANT in the way you described-- with a cascading model. We have a
> project that contains many sub-projects. We built a build_.xml
> file in the appropriate directories for each sub-project. Then, at the
> main root of the project, we use a
, 2001 5:55 AM
Subject: Includes within ANT
> I think I may have found a deficiency in ANT - in the old days of Unix
> Makefiles it was common to structure Makefiles in such a way that you would
> "include" various targets and attributes for use within other Makefiles. I
> ca
cc: (bcc: Jason Weiss/SYBASE)
Subject: Includes within ANT
I think I may have found a d
On Fri, 20 Apr 2001, Baldry, Scot M wrote:
> instead I would like to include something like "infra.xml" within every
> build file - this will ensure that the entire tree build with consistent
> infrastructure. Short of writing my own task I can't see how I can achieve
> this. The "ant" task seems
I think I may have found a deficiency in ANT - in the old days of Unix
Makefiles it was common to structure Makefiles in such a way that you would
"include" various targets and attributes for use within other Makefiles. I
can't seem to find a way to do this within ANT (the ant task is not quite
wh
