I am having problems using a nested <srcfile /> element in an apply task
like this:

<apply executable="C:\Program Files\Microsoft Visual Studio\VB98\vb6.exe"
parallel="false">
        <arg value="/m" />
        <fileset dir="c:\ant\test\src">
                <patternset>
                        <include name="*.vbp" />
                </patternset>
        </fileset>
        <srcfile />
        <arg value="/out" />
        <arg value="c:\ant\test\errors.txt" />
        <arg value="/outdir" />
        <arg value="c:\ant\test\bin" />
</apply>

The problem seems to be that the <srcfile /> value is not inserted between
the arguments in the way that I would expect from the documentation.  This
is shown by part of the -verbose output:

[apply] "C:\Program Files\Microsoft Visual Studio\VB98\vb6.exe" /m /out
c:\ant\test\errors.txt /outdir c:\ant\test\bin

I want to get the sourcefile to appear as an argument between the /m and
/out arguments.

When I remove the <srcfile /> tag the verbose output shows the inclusion of
the sourcefile value, at the end of the command as you would expect:

[apply] Executing "C:\Program Files\Microsoft Visual Studio\VB98\vb6.exe" /m
 /out c:\ant\test\errors.txt /outdir c:\ant\test\bin
C:\ant\test\src\Registry\Registry.vbp

I fear that I am missing something obvious, and have read the docs carefully
and checked the distribution list archive for similar problems.  So far I
have drawn a blank.

Anyway, suggestions/observations are warmly received!

Thanks,

Toby.

--------------------------
Toby Poulter
KPMG Consulting NZ Ltd.
Telephone: +64 9 363 3589
Mobile: +64 21 277 2605
Facsimile: +64 9 367 5873
Email: [EMAIL PROTECTED]




Disclaimer: 
The information in this electronic mail message is confidential and may be legally 
privileged. It is intended solely for the addressee. Access to this Internet 
electronic mail message by anyone else is unauthorised.  
If you are not the intended recipient, any disclosure, copying, distribution or any 
action taken or omitted to be taken in reliance on it is prohibited and may be 
unlawful.
When addressed to our clients any opinions or advice contained in this Internet 
electronic mail message are subject to the terms and conditions expressed in the 
governing KPMG client engagement letter.

KPMG accepts no responsibility for any effects this email message or attachments has 
on the recipient network or computer system.

Reply via email to