Rebo, Alex wrote:
Indeed. O'Reilly's "Ant" is a good reference
(except contrib, which was intentionally omitted; not clear "why", however;
it deserved an "honorable mention" at least).
And supplements manual (that tells a lot about the manual itself:
if you need 300 extra pages to explain
Hi,
the xslt task also works with resources to some extent.
It should be able to process a set of XML files nested in a zip as
input, using a stylesheet which is also nested in a jar or available
on an http server as a transformation.
Antoine
On Jan 17, 2007, at 1:03 PM, Matt Benson wrote
Use the uri attribute of (type/task)def, for example:
p is @{p}
In ant 1.7.0, one can drop the resource, for example:
peter
Thank you once again, Peter.
Would it be beneficial to specify
xmlns:ac="ant
(per installation instructions):
?
-Original Message-
From: Peter Reilly [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 17, 2007 12:18
To: Ant Users List
Subject: Re: Invoking a target (Ant 1.7) in a loop (A
> 1. it's resource aware,but only file resources work;
Should I use this as a blessing to go ahead with The BIG Loop?
Look, Steve, at this point ( just started with Ant) I can't express an
educated opinion
and parasiting on other's source.
>
> Well, I already expressed my concerns regarding "
I haven't been following this discussion too closely,
but I saw resources and my name... ;)
--- Steve Loughran <[EMAIL PROTECTED]> wrote:
> Rebo, Alex wrote:
> >> well, I dont think you need to do any big loops
> or iteration. You can do
> >> a bulk verify too, using verifyproperty=true
> >
>
e?
PS.: Could you, please, elaborate on "In Ant 1.7, many support resources,
which provides you
even more ways to source data."?
-Original Message-----
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 17, 2007 06:02
To: Ant Users List
Subject: Re: Invoking a t
Rebo, Alex wrote:
well, I dont think you need to do any big loops or iteration. You can do
a bulk verify too, using verifyproperty=true
The BIG loop was brought in because it is not clear whether
>
> will failfast after the first unsuccessfull iteration.
Interesting point.
(pau
> well, I dont think you need to do any big loops or iteration. You can do
> a bulk verify too, using verifyproperty=true
The BIG loop was brought in because it is not clear whether
will failfast after the first unsuccessfull iteration.
While does NOT allow inside, it is not clear
Rebo, Alex wrote:
Thank you, Steve!
In my mind the "if-then-else" block looks cleanly this way.
On top, target contra to macrodef can be executed conditionally
(if/unless)
You are correct pointing out that if a target can't be invoked all by itself
(answer to your Q: "do you ever execute ant
orse the effort, Steve?
PS.: Could you, please, elaborate on "In Ant 1.7, many support resources,
which provides you
even more ways to source data."?
-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 17, 2007 06:02
To: Ant Users Lis
Rebo, Alex wrote:
Hello!
In attempt to compute checksums for all files in a directory I wrote this:
.
inheritall="true">
Created checksum file for ${fileToWorkOn}.
I want to ask an even silli
PROTECTED]
Sent: Tuesday, January 16, 2007 15:15
To: Ant Users List
Subject: Re: Invoking a target (Ant 1.7) in a loop (Ant-Contrib)
Just curious, but why not make computeCheckSum a macrodef instead of a
target? Does it ever "stand on its own" or is it sorta a functional
unit to be called
Don't know much about macrodef, but will give it a try.
Thanks for the hint!
-Original Message-
From: Scot P. Floess [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 16, 2007 15:15
To: Ant Users List
Subject: Re: Invoking a target (Ant 1.7) in a loop (Ant-Contrib)
Just curious, bu
Looks like it works indeed!! Thank you, Dominique!
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 16, 2007 15:28
To: Ant Users List
Subject: Re: Invoking a target (Ant 1.7) in a loop (Ant-Contrib)
> Looks like it's calling it
Looks like it's calling itself via [antcall]. Is suppose to do that when
target is invoked in a loop?
Yes. The newer/faster/better task (from Ant-Contrib as well)
does not use , OTOH. Instead of always computing the
checksum, you could also use (from Ant-Contrib still), to
only update the sum
Just curious, but why not make computeCheckSum a macrodef instead of a
target? Does it ever "stand on its own" or is it sorta a functional
unit to be called? By that, I mean do you ever execute ant using that
as a target or is it a utility type thing?
Rebo, Alex wrote:
Hello!
In attempt t
17 matches
Mail list logo
