>>> > bat files are not executable, use cmd.exe instead and the bat as
>>> > argument.
>>> > See FAQ and (1.7) manual.
>>>
>>> I've been thinking about this. Why dont we have Exec complain if we
>>> find a .bat or .cmd at the end of an executable on windows?
>>
>> Because one can execute some ba
Peter Reilly wrote:
On 10/27/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
>> build.bat is called by the buildApp.xml with :
>>> failifexecutionfails="false" failonerror="false">
>
>
> bat files are not executable, use cmd.exe instead and the bat as
> argument.
On 10/27/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
>> build.bat is called by the buildApp.xml with :
>>> failifexecutionfails="false" failonerror="false">
>
>
> bat files are not executable, use cmd.exe instead and the bat as
> argument.
> See FAQ and (1.7) m
[EMAIL PROTECTED] wrote:
build.bat is called by the buildApp.xml with :
failifexecutionfails="false" failonerror="false">
bat files are not executable, use cmd.exe instead and the bat as
argument.
See FAQ and (1.7) manual.
I've been thinking about this. Why dont we have Exec complain
>build.bat is called by the buildApp.xml with :
>failifexecutionfails="false" failonerror="false">
bat files are not executable, use cmd.exe instead and the bat as
argument.
See FAQ and (1.7) manual.
> [exec] BUILD FAILED
> [exec] Target `610 Builds' does not exist in this project.
F
howdy:
In an automated build execution I have the following set up
c:\appName
where there is a build.bat and buildApp.xml
buildApp.xml is called and a PVCS call recreates the project in
c:\appName\appName, then calls the build.bat that executes the build.xml
at the root of c:\appName\appName,
