Sorry--in Ant trunk this works as posted--I thought maybe in 1.7.1 as well, so
upgrade if you're on 1.7.0! :) Otherwise, you can use:
Regards,
Matt
--- On Fri, 4/10/09, Lucas Albers wrote:
> From: Lucas Albers
> Subject: RE: fail task if subdirectories do not exist.
> To: "'Ant Users Li
This error occurs:
/tmp/build2.xml:22: restrict doesn't support the nested "type" element.
-Original Message-
From: Matt Benson [mailto:gudnabr.
This error occurs:
/tmp/build2.xml:22: restrict doesn't support the nested "type" element.
-Original Message-
From: Matt Benson [mailto:gudnabr.
> To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
> > For additional commands, e-mail: user-h...@ant.apache.org
> >
> >
> >
>
>
>
>
> -
> To
I don't get this Matt. Can you fix the following to be what you're talking
about:
To me, I don't see any way to get to another target once it fails out of one.
The onsuccess, yes, but not onfailure...
Thanks for having patience with me Matt!
Francis,
have a look at
http://ant.apache.org/manual/OptionalTasks/junitreport.html
html reports are great!
regards
supareno
Hello,
We use ant's task, and we would like to know, at the end of the run:
* how many tests were run,
* how many have succeeded,
* how many have failed,
* how many
On 2009-04-09, Gavin wrote:
> Great, thanks. My main problem stemmed from the fact I did an 'apt-get
> install ant' on the Ubuntu machines, thinking it would be a complete
> installation. In fact doing it this way and I did not get *any* jars
> whatsoever (in /usr/share/ant/lib), those you saw in
--- On Fri, 4/10/09, Eric Fetzer wrote:
> From: Eric Fetzer
> Subject: Re: onsuccess or onfailure
> To: "Ant Users List"
> Date: Friday, April 10, 2009, 9:32 AM
> Sorry, I should have given you more
> detail. It does exactly what it says. When the build
> fails (i.e. a target that isn't set
Sorry, I should have given you more detail. It does exactly what it says.
When the build fails (i.e. a target that isn't set for onfailure="false" fails)
or finishes with success, it immediately calls the target specified. In my
example, it would call either the onsuccess or onfailure targets
Hello,
We use ant's task, and we would like to know, at the end of the run:
* how many tests were run,
* how many have succeeded,
* how many have failed,
* how many have returned an error.
Apart from scanning the ant output itself to count "by hand" (well, using
perl), is there another way (an
Hi all,
I've got a generic build process working, but I'd like to iterate it over a
set of users in order to create a per-user specific build (with its own
configuration). The solution that came into my mind is to create a set of ant
files with the properties of each user (e.g., profile1.xml wit
11 matches
Mail list logo
