On 11/28/07, Agarkar, M (Milind) <[EMAIL PROTECTED]> wrote:
> Thanks Jan.
> Any idea about how to trap a PID on-the-fly ? It would be a script to run
> automatically.
>
In snapshot testing we use the next targets to find and kill hung VMs
after a suite run.
PROCESSES: ${proccess}
Oh I get it now! You're running ant from inside VIM. Therefore, the swap
files exist.
You can add them to your default excludes. I had to do that because in our
CVS, someone put a bunch of empty .keepme files. I guess the idea is to keep
the directory if there was no files in it.
Simple enough to
I finally got the commenting of zip files working the way I want but am still
having to add a file to the zip to get the comment added. I create the list of
zip files as a property file:
,${__zFileToAdd}
Thanks that's a very useful answer. :)
--- Steve Loughran <[EMAIL PROTECTED]> wrote:
> Xavier Outhier wrote:
> > Hi all,
> >
> > I was not successful searching a resource where would be listed the
> > possible error when
> running an
> > ant task.
> > For instance when running cvs task error=2
Xavier Outhier wrote:
Hi all,
I was not successful searching a resource where would be listed the possible
error when running an
ant task.
For instance when running cvs task error=2 mean that cvs.exe is not in the path.
There's no easy way to predict these, as they come from the OS, not Ant
Hi all,
I was not successful searching a resource where would be listed the possible
error when running an
ant task.
For instance when running cvs task error=2 mean that cvs.exe is not in the path.
Could someone give me an hint?
Thank you,
Xavier.
Dimitris Mouchritsas wrote:
No, but I run ant from within vim, much like an ide. So they're still there
when I create the jar. I just thought that they were on the default
excludes.
not on the defaults; you can always add them.
-
No, but I run ant from within vim, much like an ide. So they're still there
when I create the jar. I just thought that they were on the default
excludes.
On Dec 2, 2007 2:50 AM, David Weintraub <[EMAIL PROTECTED]> wrote:
> The JAR task doesn't look at the source files, but at the contents that is
