RE: Exec task question

We've created a separate VOB/share/whatever you want to call it that contains all of the re-usable tools we use throughout our team. This way, we know exactly where these files are in a relative path from any build script. ie: root share of cvs | +-- sw (contains active source code) | +-- sw-t

RE: exec task with bad args

Thanks, worked fine; -Original Message- From: Stefan Bodewig [mailto:[EMAIL PROTECTED]] Sent: 19 November 2002 12:24 To: [EMAIL PROTECTED] Subject: Re: exec task with bad args "|" is just another way of shell

Re: exec task with bad args

"|" is just another way of shell redirects: Stefan -- To unsubscribe, e-mail: For additional commands, e-mail:

RE: exec task

Thanks! I should have thought of that. But, fyi, I had to use instead of Thanks, -Original Message- From: Anakreon Mejdi [mailto:amejdi@;ertonline.gr] Sent: Friday, November 08, 2002 10:19 AM To: Ant Users List Subject: Re: exec task You should pass the params to bash or your

Re: exec task

You should pass the params to bash or your favorite shell instead of echo. Buonassisi, Vincent [Contractor] wrote: Hi, I am trying to get the exec task to create the command echo ESS.5.4.03 | sed '...' and execute it. Instead, it looks like the exec task is creating

Re: exec task dir attribute

--- [EMAIL PROTECTED] wrote: > anyone have problems getting the exec task to execute a command under > the directory specified in the dir attribute? The 'dir' attribute points to the directory in which the command will be executed, not the directory in which to find the command that's being execu

Re: exec task args

ECTED]] Sent: Monday, June 18, 2001 7:42 PM To: ant-user Cc: rjohn Subject: Re: exec task args I am trying to integrate ant with our proprietary tools which I intend to call from the ant build.xml. I want to specify the work areas to create for fetching source and building as command line a

Re: exec task args

Ok, the -D input had a typo in it. It's working now. Thanks. "Larry V. Streepy, Jr." wrote: > I would run ant -debug so you can see exactly how the properties are > being set and what the resulting exec command is. > > I'm assuming that you're invoking ant something like this: > > ant -Dsome.

RE: exec task args

Run ant with the -v flag, or the -debug flag to see some indications of what Ant is up to. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, 19 June 2001 10:42 AM > To: [EMAIL PROTECTED] > Subject: Re: exec task args &g

Re: exec task args

I would run ant -debug so you can see exactly how the properties are being set and what the resulting exec command is. I'm assuming that you're invoking ant something like this: ant -Dsome.path=/some/path -Dsome.value=some_value Correct? Ruby John wrote: > > I am trying to integrate ant with

Re: exec task args

I am trying to integrate ant with our proprietary tools which I intend to call from the ant build.xml. I want to specify the work areas to create for fetching source and building as command line arguments to ant. The program that I am uting is complaining about the invalid character: "{" which it

Re: exec task args

If you're defining both some.path and some.value using -D flags to ant, then what you wrote should work fine. Can you be a little more detailed on what you want to accomplish? Ruby John wrote: > > How do I get property or path variables to be expanded when passing > arguments to a task? > >

Re: exec task timeout kill doesn't work properly

Rudolf Balada <[EMAIL PROTECTED]> wrote: > I have a problem with exec task timeout. When the timeout comes to > kill the process he started, it kills only the process he > started. The kill doesn't affect child processes which should be > also killed. Hmm, Ant invokes java.lang.Process.destroy()