lto:[EMAIL PROTECTED]
Sent: Wednesday, October 25, 2006 11:49 AM
To: Ant Users List
Subject: RE: AW: dynamic targets
Thanks to you all for your comments. I guess I finally did get my point across
and you all came up with interesting options. I try to avoid writing custom
tasks and such if I
tion. Curiously enough, I
already employ this technique for imports that provide optional functionality.
I guess I was so focused on figuring out how to implementing dynamic targets
that I missed the relevant application here. It still requires me to
exhaustively specify every possible top-le
On 10/25/06, Mathew Delong <[EMAIL PROTECTED]> wrote:
Like others said, failonerror="false" (someone mistyped this and
said "true" but meant false)
Thanks for the correction.
One very easy solution I see is in every "individual" build file include a line
like:
This fulfills your requiremen
ROTECTED]
Sent: Tuesday, October 24, 2006 10:58 PM
To: Ant Users List
Subject: Re: AW: dynamic targets
At 08:05 AM 10/24/2006, you wrote:
>same - write a common buildfile (maybe with
empty implementation) and all the
>projects have all needed targets. Web project could overwrite the
>
Yep, is powerful and extremely useful
and I use it all the time. I tried to keep my
example specific and concrete so as not to
complicate the question. But it seems to have
caused the original point of this exercise to be entirely missed.
Indeed. Yet now that I understand what you are after,
There are two "subbuildfiles" - both contain target "one", but only the first
has a target "three".
Jan
>-Ursprüngliche Nachricht-
>Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Gesendet: Mittwoch, 25. Oktober 2006 06:57
>
cht-
>Von: Jacob Kjome [mailto:[EMAIL PROTECTED]
>Gesendet: Mittwoch, 25. Oktober 2006 04:58
>An: Ant Users List
>Betreff: Re: AW: dynamic targets
>
>At 08:05 AM 10/24/2006, you wrote:
> >same - write a common buildfile (maybe with empty
>implementation) and all
emore
icouldkeepgoing
youthinkicant
doyoudoubledogdareme
okyougotitmister
imstillgoing
youaskedforitandyougotit
onemorejustforoldtimesake
wowthisisstartingtogetannoyingnow
yepreallyannoying
butforsomereasonijustcantstop
okillstop
justforyou
hehgotchastillgoing
okimsickofwriting
illstop
Default target:
On 10/24/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
same - write a common buildfile
Can I say me too? ;-) is a good solution I think.
FTR, I did in the past create targets dynamically, just so they were ordered
dynamically (along internal module dependency lines), but this was hackish
r 2006 09:13
>An: Ant Users List
>Betreff: Re: dynamic targets
>
>Hello Jacob,
>
>why don't you just import a common build file and define the
>common target there. Only when the target is not defined in
>the build file, the common target gets executed.
>
>R,
&
Kjome <[EMAIL PROTECTED]>
An: user@ant.apache.org
Betreff: dynamic targets
>
> Along the lines of
> http://marc.theaimsgroup.com/?l=ant-user&m=107429941032345&w=2
>
> Is it possible to create targets dynamically, deferring creation
> until such time as it i
Along the lines of
http://marc.theaimsgroup.com/?l=ant-user&m=107429941032345&w=2
Is it possible to create targets dynamically, deferring creation
until such time as it is found that the project doesn't have the
target already defined? My use-case is using to iterate
over sub-builds cal
12 matches
Mail list logo
