>>> From ant.apache.org:-
>>>
>>> 1) select the link "manual" under documentation.
>>> 2) select the link "Apache Ant" in the text on the RH frame.
>>> ant.apache.org then opens up within that frame.
>>> 3) Now repeat the procedure which continues to open frame-after-
>>> frame across RH side
On Tue, 28 Feb 2006, Steve Meredith <[EMAIL PROTECTED]> wrote:
> Not sure who to contact about the ant.apache website itself...no
> clues (even after following help instructions for contact) on site
> :-|
I think the user or dev lists are the appropriate contacts.
>> Whilst surfing around ant.ap
Stefan Bodewig wrote:
On Thu, 23 Feb 2006, Vishal Vishnoi <[EMAIL PROTECTED]> wrote:
Thus, the above can be the default, as it's simple and work for most
people. AntUnit should consider providing an attribute which make
naming a combination of project and target name. Here's an example
Hello
--- Paul Faulstich <[EMAIL PROTECTED]> wrote:
>
> Is there a way to tell if a fileset is empty? If
> so, he could just create a fileset based on that dir
> and check it. I haven't found such a task if there
> is one.
Yes, there is a way to tell if a fileset is empty: use
task with its se
Just trying to change things to see if it fixes it or if it caused the
symptoms to change to perhaps something more obvious, I changed the ant task
to use passive ftp. Still fails randomly after a while each run. But now I
get this error message each time.
Can someone interpret this? What addre
Rhino,
Thanks for the reply. I'm certain the space is there. Also, the first time
it transferred a bunch of files and hung. Restarted and it transferred a
bunch more files before it hung, etc. Ditto several times. If it was a
target space problem, I suspect it would hit a wall at the same file
I had similar behaviour several weeks back when I tried to FTP a much
smaller number of files, no more than 200. I don't recall if I got no
message at all or just a very vague and misleading one.
It eventually turned out that the server which was receiving the files had
filled up. It was just
I have an ant script that date checks and FTPs several thousand files. Ant
gets a portion of the way through it and hangs (I run -verbose). I'll run
it again, and it'll get further (apparently because more files have already
been transferred each iteration), then hang again. But it appears to be
I think Eric is really asking - if you have a directory (which may be empty or
may contain files, subdirectories, etc), how do you tell if that directory is
empty or not?
He states in his first message that he wants to know this because tar fails if
you try to tar an empty directory. You could
On Thu, 23 Feb 2006, Vishal Vishnoi <[EMAIL PROTECTED]> wrote:
> Thus, the above can be the default, as it's simple and work for most
> people. AntUnit should consider providing an attribute which make
> naming a combination of project and target name. Here's an example
>
>
I'd rather want to m
On Thu, 23 Feb 2006, Vladimir Egorov <[EMAIL PROTECTED]> wrote:
> The absolute path to build file depends on the system.
Agreed.
> In JUnit, the fully-qualified class name does not depend on the
> system.
I'm with Vishal here, the project name probably maps better to the
fully qualified class n
Hi
Not sure who to contact about the ant.apache website itself...no
clues (even after following help instructions for contact) on site :-|
but thought you might like to know
Regards
Steve
P.S. this is my last attempt at contacting someone at ant.apache
about a fault that might help t
Jan
>-Ursprüngliche Nachricht-
>Von: Eric Wood [mailto:[EMAIL PROTECTED]
>Gesendet: Dienstag, 28. Februar 2006 17:37
>An: Ant Users List
>Betreff: RE: Check if files exist in a folder before I tar
>
>I don't know the names of the files in the directory. I want
>to
I don't know the names of the files in the directory. I want to determine if
there are any files in the directory before I attempt to tar.
Eric
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 28, 2006 10:52 AM
To: user@ant.apache.org
Subject
Steve,
> Ant doesnt set the name of the target. What happens if there is more
> than one target on the command line? What if you are being called from
> an outer build file that has different names? It wouldn't scale.
makes sense.
> use a property:
>
> ant -f generic.build -Dtarget=cdrom
yep, w
Jan
>-Ursprüngliche Nachricht-
>Von: Eric Wood [mailto:[EMAIL PROTECTED]
>Gesendet: Dienstag, 28. Februar 2006 16:50
>An: user@ant.apache.org
>Betreff: Check if files exist in a folder before I tar
>
>What is the easiest way to check if files exist in a folder
>prior to attemp
What is the easiest way to check if files exist in a folder prior to
attempting to back them up via tar?
Tar fails if I run it asking it to back up files and no files exist.
Eric
[EMAIL PROTECTED] wrote:
Jan and I are both producing the same answer. Here's the overlap:
yepp ;-)
In earlier times (prior to Ant 1.6) this was the only possibility to do
more
difficult initializations because only a few tasks were allowed to be
outside
of a .
Since 1.6 you could do (nearly
Jakob Fix wrote:
Hi Alex,
On 2/28/06, schmaxelander <[EMAIL PROTECTED]> wrote:
Hi Jakob,
what exactly is your question?
If the target is available from commandline, its available from within
the script, too. What is you error message? Did you really name your
script file "generic.build"?
I'm
Jan, thanks for this. I appreciate it.
Still, searching my year-long-or-so gmail ant-users account containing
a couple of thousand messages for terms as generic in the context of
ant as "property", "target" and "name" yields so many unrelated
results that it's difficult to find the "Nadel im Heuh
Did you had a look at ?
Jan
>-Ursprüngliche Nachricht-
>Von: Jakob Fix [mailto:[EMAIL PROTECTED]
>Gesendet: Dienstag, 28. Februar 2006 16:40
>An: Ant Users List
>Betreff: Re: command line target available from inside build script?
>
>Hi Alex,
>
>On 2/28/06, schmaxelander <[EMAIL PROTECT
Hi Alex,
On 2/28/06, schmaxelander <[EMAIL PROTECTED]> wrote:
> Hi Jakob,
>
> what exactly is your question?
> If the target is available from commandline, its available from within
> the script, too. What is you error message? Did you really name your
> script file "generic.build"?
I'm not havin
>sure I did. however, searching for "property target available ant"
>does not necessarily return a satisfying answer.
>
>http://ant.apache.org/manual/using.html#built-in-props
>doesn't list the target property or something similar ...
>
>sorry for looking in the wrong places :-)
A search inside th
Jan,
On 2/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I guess you havent searched yet?
sure I did. however, searching for "property target available ant"
does not necessarily return a satisfying answer.
http://ant.apache.org/manual/using.html#built-in-props
doesn't list the target prop
I guess you havent searched yet?
Jan
>-Ursprüngliche Nachricht-
>Von: Jakob Fix [mailto:[EMAIL PROTECTED]
>Gesendet: Dienstag, 28. Februar 2006 16:09
>An: Ant Users List
>Betreff: command line target available from inside build script?
>
>Hi,
>
>I was wondering whether the target given
Hi,
I was wondering whether the target given on the command line like this
ant -f generic.build server
(i.e. "server" in this example) is available from within the ant
script, like ${target}. apparently, it's not ${target} because
otherwise I wouldn't have asked, I tried that, and yes, the
docu
>Jan and I are both producing the same answer. Here's the overlap:
yepp ;-)
In earlier times (prior to Ant 1.6) this was the only possibility to do
more
difficult initializations because only a few tasks were allowed to be
outside
of a .
Since 1.6 you could do (nearly) everything outside of a .
On Tue, 2006-02-28 at 09:24 -0500, Glen Mazza wrote:
> [EMAIL PROTECTED] wrote:
> > If you´re doing the in a init-target and let the deploy-target
> > depend on that, should work.
>
> Is there really such a thing as an "" -- I can't find it
> anywhere in the manual, and Google isn't being much of
Jan and I are both producing the same answer. Here's the overlap:
Or near enough to get you going.
James
On Tue, 2006-02-28 at 14:24, Glen Mazza wrote:
> [EMAIL PROTECTED] wrote:
>
> > If you´re doing the in a init-target and let the deploy-target
> > d
[EMAIL PROTECTED] wrote:
If you´re doing the in a init-target and let the deploy-target
depend on that, should work.
Jan
Is there really such a thing as an "" -- I can't find it
anywhere in the manual, and Google isn't being much of a friend here
either (translating "init-target" to a ve
James Abley wrote:
What scope are you doing the taskdefs for the Tomcat ANT tasks?
I guess "global" -- the s are immediate children of the
root. But I was unaware of the concept of scope in Ant --
where is it defined in the manual[1]--I can read up on this, or if
someone can give me a qu
If you´re doing the in a init-target and let the deploy-target
depend on that, should work.
Jan
>-Ursprüngliche Nachricht-
>Von: Glen Mazza [mailto:[EMAIL PROTECTED]
>Gesendet: Dienstag, 28. Februar 2006 14:55
>An: user@ant.apache.org
>Betreff: Have an Ant script run even with missing
What scope are you doing the taskdefs for the Tomcat ANT tasks?
On Tue, 2006-02-28 at 13:55, Glen Mazza wrote:
> Hello,
>
> I have an Ant build script for dynamic deployment of a web application
> to Tomcat. This requires a special Tomcat JARs to be added to the Ant
> lib directory to run. No
Hello,
I have an Ant build script for dynamic deployment of a web application
to Tomcat. This requires a special Tomcat JARs to be added to the Ant
lib directory to run. No problem here--Ant runs fine once I add the jar.
But I have small additional target unrelated to deployment I would lik
>Will the value of 'xsl.file' always be interface.xsl?
No. Can be overridden while starting with
ant -Dxsl.file=another.stuff
>Also does the value of matter since 'xml.file' in
> has the value.
Manual::CoreTasks::Condition-Supported conditions
available
This condition is identical to
Hi,
Will the value of 'xsl.file' always be interface.xsl?
Also does the value of matter since 'xml.file' in
has the value.
cheers,
//mikael
36 matches
Mail list logo
