Hmm... Antunit seems to be giving me bogus results. It should fail,
but it doesn't. Try the following build file. First try running the
default target, "main", under either Ant-1.6.5 or Ant-1.7.0. Notice
that the property for ${app.m} remains unresolved and ends up as the
literal value "$
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
On 1/5/07, Rebhan, Gilbert <[EMAIL PROTECTED]> wrote:
Hi,
can you give a short snippet to illustrate your problem ?
i use limit like that and it works fine =
put all my stuff that should be killed
if not in time, f.e.
...
...
if there are any sideeffects with your targets and antca
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
-- Forwarded message --
From: Peter Reilly <[EMAIL PROTECTED]>
Date: Jan 17, 2007 6:55 PM
Subject: Re: Invoking a target (Ant 1.7) in a loop (Ant-Contrib)
To: "Rebo, Alex" <[EMAIL PROTECTED]>
On 1/17/07, Rebo, Alex <[EMAIL PROTECTED]> wrote:
So many thanks, Peter!
One "smart" Q
Thanks Peter.
> No,
> It is not provided to the build script.
>
> Peter
>
>
> On 1/17/07, Andre Dantas Rocha <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Suppose I type this command in command line: "ant TARGET_NAME
> > -Dambiente=dev"
> >
> > Is that possible to get the target name (TARGET_NAME in
So many thanks, Peter!
One "smart" Q, however:
Ability to provide qualified name space,
such as in
,
should be granted by smth like:
xmlns:ac="antlib:net.sf.antcontrib"
Where that "smth" should be specified, provided my reference to antcontrib
is set (per installation instructions):
No,
It is not provided to the build script.
Peter
On 1/17/07, Andre Dantas Rocha <[EMAIL PROTECTED]> wrote:
Hi,
Suppose I type this command in command line: "ant TARGET_NAME -Dambiente=dev"
Is that possible to get the target name (TARGET_NAME in this case) inside my
build?
Thanks,
Andre
Quoting Steve Loughran <[EMAIL PROTECTED]>:
> Jacob Kjome wrote:
> > Quoting Steve Loughran <[EMAIL PROTECTED]>:
>
> >
> > No, I get the same behavior in Ant-1.6.5. I think this is a longstanding
> issue.
>
> uh oh. those are bad. Theres more of a risk that someone has been
> depending on it.
>
Hi,
Suppose I type this command in command line: "ant TARGET_NAME -Dambiente=dev"
Is that possible to get the target name (TARGET_NAME in this case) inside my
build?
Thanks,
Andre
> 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
> >
>
Asking this question again. Is there anyway to force-load a diffrent
property file in Anthill project property sheet even the build.xml loads one
by default?
In the build.xml file I already tell it to load .build.properties and on a
DOS cmnd line I can supercede it by doing ant -propertyfile
On 1/17/07, Rebo, Alex <[EMAIL PROTECTED]> wrote:
Thank you, Steve!
The idea was to "unload" the heavy construct such as:
...
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
Thank you, Steve!
The idea was to "unload" the heavy construct such as:
...
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
Thanks for the help yesterday, guys.
Its resolved now.
The variable which I was not able to access, was being set,
but not being exported in .profile.
*embarrassed* :(
-Original Message-
From: Kalsi, Ramnish
Sent: 16 January 2007 13:37
To: Ant Users List; [EMAIL PROTECTED]
Subject: R
Jacob Kjome wrote:
Quoting Steve Loughran <[EMAIL PROTECTED]>:
No, I get the same behavior in Ant-1.6.5. I think this is a longstanding issue.
uh oh. those are bad. Theres more of a risk that someone has been
depending on it.
have a look at the source and see if you can find a proble
21 matches
Mail list logo
