On Fri, Jun 26, 2009 at 15:21,
andrewdanger<andrewdangermuro+nab...@gmail.com> wrote:
>
> yeah, this is an option, but i need it all in a script because i need to do
> non-ant things and i find it easier to do non-ant things in bash rather than
> with the <exec> task. anyway, i did find the solution, which is to escape
> newlines in the command output:
>
Err...
<exec executable="/bin/bash" failonerror="true">
<arg value="${the.script}"/>
<arg value="arg1tothescript"/>
<!-- and so on -->
</exec>
--
Francis Galiegue
ONE2TEAM
Ingénieur système
Mob : +33 (0) 683 877 875
Tel : +33 (0) 178 945 552
f...@one2team.com
40 avenue Raymond Poincaré
75116 Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-h...@ant.apache.org
