--- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> Note that only CVS HEAD will search nested ,
> the 1.6 branch
> won't since I've only added it when I created the
> task.
Good thing I only added it to HEAD then, eh?
-Matt
__
Do you Yahoo!?
Yahoo!
On 10 Sep 2004, <[EMAIL PROTECTED]> wrote:
> Added searchpath attribute to for searching path
> variables when resolveexecutable = true. Thanks to Stefan
> for having already written the path-searching code.
Note that only CVS HEAD will search nested , the 1.6 branch
won't since I've only
On Tue, 29 Jul 2003, Steve Loughran <[EMAIL PROTECTED]> wrote:
> Maybe the trick is to start a java spawner program (ours), that sets
> up stdio, does the pumping, etc, etc.
Probably.
It would have to be forked and to be save invoked via nohup on Unix
systems, though. So there still would be so
On Wed, 30 Jul 2003, Antoine Levy-Lambert <[EMAIL PROTECTED]>
wrote:
> Where in the code does the executable get resolved if
> vmlauncher=false ?
Nowhere, the OS does.
If you look at antRun for example, it does
,
| cd "$1"
| CMD="$2"
| shift
| shift
|
| exec "$CMD" "$@"
`
which means
- Original Message -
From: "Stefan Bodewig" <[EMAIL PROTECTED]>
Sent: Wednesday, July 30, 2003 1:26 PM
> On Wed, 30 Jul 2003, Antoine Levy-Lambert <[EMAIL PROTECTED]>
> wrote:
>
> > Sorry,
>
> No harm done.
>
> > I will roll-back my change.
>
> Thanks. Maybe we can take what you've writ
On Wed, 30 Jul 2003, Antoine Levy-Lambert <[EMAIL PROTECTED]>
wrote:
> Sorry,
No harm done.
> I will roll-back my change.
Thanks. Maybe we can take what you've written (which I guess is
correct for vmlauncher="true") and what is present in the vmlauncher
docs and combine it to something sensib
Sorry,
I will roll-back my change.
Antoine
- Original Message -
From: "Stefan Bodewig" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 30, 2003 12:27 PM
Subject: Re: cvs commit: ant/docs/manual/CoreTasks exec.html
> On 30 Jul 2003,
On 30 Jul 2003, <[EMAIL PROTECTED]> wrote:
> added precisions regarding the executable attribute in the
> task
This is not correct. Please see the blurb about relative paths in the
description of the vmlauncher attribute.
If you set vmlauncher to false, your CWD will be set to the dir
attr
Stefan Bodewig wrote:
On Tue, 29 Jul 2003, Antoine Levy-Lambert <[EMAIL PROTECTED]>
wrote:
I do not know at all what is going to happen with output, error,
stdin for the spawned process.
My guess is they cause trouble if the spawned process wants to use
them. I should back that claim, maybe late
On Tue, 29 Jul 2003, Antoine Levy-Lambert <[EMAIL PROTECTED]>
wrote:
> I do not know at all what is going to happen with output, error,
> stdin for the spawned process.
My guess is they cause trouble if the spawned process wants to use
them. I should back that claim, maybe later today/tomorrow.
> On Tue, 29 Jul 2003, Conor MacNeill <[EMAIL PROTECTED]>
> wrote:
>
> >> (2) the spawned process to be stoped or even killed by the system
> >> (at least Unix) as soon as it tries to write to stdout or stderr
> >> (probably either with SIGTTOU, SIGPIPE or SIGHUP).
> >
> > Why not just "caveat us
- Original Message -
From: "Stefan Bodewig" <[EMAIL PROTECTED]>
Sent: Tuesday, July 29, 2003 9:42 AM
> On 28 Jul 2003, <[EMAIL PROTECTED]> wrote:
>
> > in the sense that I do not connect at all the new process to
> > stream handlers and the ant logging system, disabling input,
> >
,
Antoine
- Original Message -
From: "Stefan Bodewig" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 29, 2003 9:43 AM
Subject: Re: cvs commit: ant/docs/manual/CoreTasks exec.html
> On 28 Jul 2003, <[EMAIL PROTECTED]> wrote:
>
> > Th
On Tue, 29 Jul 2003, Conor MacNeill <[EMAIL PROTECTED]>
wrote:
>> (2) the spawned process to be stoped or even killed by the system
>> (at least Unix) as soon as it tries to write to stdout or stderr
>> (probably either with SIGTTOU, SIGPIPE or SIGHUP).
>
> Why not just "caveat user" :-)
AFAIU t
On Tue, 29 Jul 2003 05:42 pm, Stefan Bodewig wrote:
> On 28 Jul 2003, <[EMAIL PROTECTED]> wrote:
> > in the sense that I do not connect at all the new process to
> > stream handlers and the ant logging system, disabling input,
> > output, error, and return exec attributes in the case of spawn
On 28 Jul 2003, <[EMAIL PROTECTED]> wrote:
> This change allows exec to start a process which will run
> independently of ant.
Will the spawned process keep running after Ant is finished?
Stefan
-
To unsubscribe, e-mail: [E
On 28 Jul 2003, <[EMAIL PROTECTED]> wrote:
> in the sense that I do not connect at all the new process to
> stream handlers and the ant logging system, disabling input,
> output, error, and return exec attributes in the case of spawn.
Won't this cause
(1) the spawned process to hang as soo
17 matches
Mail list logo
