If you really wanted you could "break" up one big build.xml into a set of
smaller .xml files and use the task to bring them all back together at
run-time...
"Frank W. Zammetti" <[EMAIL PROTECTED]> wrote:
Not really... each target performs a specific task, and the one main
target antcalls all t
Not really... each target performs a specific task, and the one main
target antcalls all the others in the proper sequence. It's really no
more complicated than a series of method calls. Each target, or method
in the analogy, is fairly small and simple, there just happens to be a
fair number
On 7/31/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> 50 lines?
>
> I have one script that is upwards of 700 lines. I wouldn't worry about
> 50 ;)
>
> Frank
How do you organize that? 700 lines is just way too big to read, isn't it?
-Thufir
--
50 lines?
I have one script that is upwards of 700 lines. I wouldn't worry about
50 ;)
Frank
THUFIR HAWAT wrote:
On 7/31/05, Andrew Goktepe <[EMAIL PROTECTED]> wrote:
The 'ant' task might be what you're looking for - it works like antcall, but
on a separate build file.
http://ant.apache.o
On 7/31/05, Andrew Goktepe <[EMAIL PROTECTED]> wrote:
> The 'ant' task might be what you're looking for - it works like antcall, but
> on a separate build file.
> http://ant.apache.org/manual/CoreTasks/ant.html
> Example:
>
> -Andrew
...
Yes, thank you. (I stumbled across that, too!) I lik
The 'ant' task might be what you're looking for - it works like antcall, but
on a separate build file.
http://ant.apache.org/manual/CoreTasks/ant.html
Example:
-Andrew
On 7/30/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
>
> Well, I'm not sure how one calls another whole script, perh
Well, I'm not sure how one calls another whole script, perhaps someone
else reading this does.
However, if they are all typical build scripts in the sense that there
is one particular target that is called to get things going, you can
certainly antcall that target in each of the scripts. That
On 7/30/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
...
> Executing build.xml results in the test2 target being executed after
> test1 is. The project name has to be different, although what you get
> looks more like a warning than an error to me, but that's the reason it
> is different above
If I understand what your asking correctly, here's an example...
build.xml:
--
build2.xml
--
Executing build.xml results in the test2 target being executed after
test1 is. The project name has to be different, although what you get
On 6/24/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> I may not have explained what I did very well...
>
> I have a base target that is like this:
>
>
>
>
>
>
>
> ...
>
>
> There's probably 10-15 more where you see the ... All the
> called targets are wit
t;
>>-Ursprüngliche Nachricht-
>>Von: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
>>Gesendet: Freitag, 24. Juni 2005 15:32
>>An: Ant Users List
>>Cc: user@ant.apache.org
>>Betreff: Re: AW: Multiple IFs, or IFs on tasks
>>
>>Thank you Jan,
>An: Ant Users List
>Cc: user@ant.apache.org
>Betreff: Re: AW: Multiple IFs, or IFs on tasks
>
>Thank you Jan, that's a good approach too.
>
>FYI, I wound up taking a simple approach, after I thought
>about this some more... I simply have an antcall from one
>target t
Thank you Jan, that's a good approach too.
FYI, I wound up taking a simple approach, after I thought about this some
more... I simply have an antcall from one target to another that checks
the second property. So it winds up being like a nested if in a sense...
I would have to explain quite a bit
Common pattern:
All conditions set
...
Jan
>-Ursprüngliche Nachricht-
>Von: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
>Gesendet: Donnerstag, 23. Juni 2005 17:42
>An: Ant Users List
>Cc: Ant Users List
>Betreff: Re: Multiple IFs, or IFs on tasks
>
>Ah, t
14 matches
Mail list logo
