Jacob Kjome:
> Versions matter. I have BSF-2.3.0.jar and
> js-1.5R3.jar in ${user.home}/.ant/lib. Using a
> later version of js.jar with BSF-2.3.0 won't
> work. If you want to use a newer version of
> javascript, then upgrade to BSF-2.4.0 and grab
> the latest js.jar. Of course, BSF-2.4.0
At 09:49 PM 1/20/2007, you wrote:
>Jacob Kjome:
>> I added my own twist on it and made dependency
>> following configurable (follows dependencies by
>> default if not specified) along with optional
>> "if" and "unless" attributes. Actually, all the
>> attributes are optional, even "target". If
>
Hi Ninju.
Ninju Bohra:
> The behavior you see is correct...there is an inherent limition of the
> task becuase it starts a new ANT "cycle" and knowlegde of
> previous run targets (like your "init" target) are not retained.
>
> You can try many different solutions:
>
> First solution:
> 1) Crea
e target:
.
(really delicate stuff that can only be run once)
.
- Original Message ----
From: Cameron McCormack <[EMAIL PROTECTED]>
To: user@ant.apache.org
Sent: Saturday, January 20, 2007 4:59:26 AM
Subject: Using antcall but not re-running
Jacob Kjome:
> I added my own twist on it and made dependency
> following configurable (follows dependencies by
> default if not specified) along with optional
> "if" and "unless" attributes. Actually, all the
> attributes are optional, even "target". If
> "target" is either not defined or d
You can do it via scripting. See this thread...
http://marc.theaimsgroup.com/?t=10758568804&r=1&w=2
...and specifically, this message...
http://marc.theaimsgroup.com/?l=ant-user&m=107589782422983&w=2
I added my own twist on it and made dependency
following configurable (follows dependenc
Hi.
I’ve got a build file that’s structured like this:
If I run "ant one" I get:
jet:/tmp $ ant one
Buildfile: build.xml
init:
[echo] something
something:
one:
init:
[echo] something
two-other:
BUIL