Hello Simon,
(In addition to the Gert's suggestion.)
>From the message, it appears it is coming from the Oracle Forms program. (I
>haven't used it before.)
Typically when I see a strange message, I would:
1) use <echo> task to print out the value of "program" and "commandline"
attribute.
2) change to the base directory, and manually execute "program" with the
"commandline" args.
This should help you reproduce the problem outside of NAnt, and hopefully give
you enough clues on what's missing.
I hope this helps.
Charles
--- On Mon, 5/24/10, Simon H <yo...@live.com> wrote:
From: Simon H <yo...@live.com>
Subject: Re: [NAnt-users] Question about <foreach> task and the failonerror
attribute
To: gert.drie...@telenet.be, nant-users@lists.sourceforge.net
Received: Monday, May 24, 2010, 7:07 AM
Perhaps there's one more mystery that you can assist me with. For the
compilation of Reports I have the following <foreach> task:
<foreach item="File" property="filename" >
<in>
<items basedir="${source.directory}\${project.type}\Reports">
<include name="*.rdf" />
</items>
</in>
<do>
<exec program="${reports.path}"
workingdir="${source.directory}\${project.type}\Reports"
commandline="userid=${username}/${passwo...@${database} batch=yes
source=${filename} stype=rdffile dtype=repfile compile_all=yes overwrite=yes
logfile=log.txt" failonerror="false" />
</do>
</foreach>
All reports compile correctly, but for some reason the output for each Report
compilation is "[exec] Could not read reports properties." I have no idea what
this is referring to and it does not appear to indicate any compilation error.
Any ideas? Thanks in advance!
From: gert.drie...@telenet.be
To: yo...@live.com; nant-users@lists.sourceforge.net
Subject: RE: [NAnt-users] Question about <foreach> task and the failonerror
attribute
Date: Mon, 24 May 2010 08:45:15 +0200
#yiv1865313835 .ExternalClass .ecxshape
{}
#yiv1865313835 .ExternalClass p.ecxMsoNormal, #yiv1865313835 .ExternalClass
li.ecxMsoNormal, #yiv1865313835 .ExternalClass div.ecxMsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'serif';}
#yiv1865313835 .ExternalClass a:link, #yiv1865313835 .ExternalClass
span.ecxMsoHyperlink
{color:blue;text-decoration:underline;}
#yiv1865313835 .ExternalClass a:visited, #yiv1865313835 .ExternalClass
span.ecxMsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
#yiv1865313835 .ExternalClass p
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;font-family:'serif';}
#yiv1865313835 .ExternalClass span.ecxEmailStyle18
{font-family:'sans-serif';color:#1F497D;}
#yiv1865313835 .ExternalClass .ecxMsoChpDefault
{font-size:10.0pt;}
_filtered #yiv1865313835 {}
#yiv1865313835 .ExternalClass div.ecxSection1
{}
Hey Simon,
You should set “failonerror” on the <exec> task instead.
Hope this helps,
Gert
From: Simon H [mailto:yo...@live.com]
Sent: maandag 24 mei 2010 8:35
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] Question about <foreach> task and the failonerror
attribute
Hi guys,
I have made a build file for the automated compilation of Oracle Forms files.
An excerpt of the code is as follows:
<target name="build" description="compiles the source code">
...
<foreach item="File" property="filename" failonerror="false" >
<in>
<items basedir="${source.directory}\${project.type}\Forms">
<include name="*.fmb" />
</items>
</in>
<do>
<exec program="${forms.path}"
workingdir="${source.directory}\${project.type}\Forms"
commandline="module=${filename} userid=${username}/${passwo...@${database}
batch=yes module_type=form compile_all=yes window_state=minimize" />
</do>
</foreach>
...
</target>
The build file navigates to the directory containing the forms that the user
desires fo compile and attempts to compile each form. The failonerror attribute
is set to false so that the build file does not exit if a compilation error
occurs. Unfortunately, however, though this prevents the build file from
exiting when a compilation error occurs, it also appears to make the build file
exit the <foreach> task. This is a problem because, unless the form that does
not compile successfully is the last to be tested (based on the filename of the
form in alphanumerical decsending order), there will be one or more forms that
the build file does not attempt to compile. So, for example, if the folder
containing the forms that are desired to be compiled contains 10 forms and the
first form does not compile successfully, the build file will not attempt to
compile the remaining 9 forms (ie exit the <foreach> task). Is there a way to
make the build file attempt to
compile remaining forms after encountering after failing to compile a form?
Thanks in advance!
Australia's #1 job site If It Exists, You'll Find it on SEEK
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.819 / Virus Database: 271.1.1/2888 - Release Date: 05/23/10
20:26:00
Australia's #1 job site If It Exists, You'll Find it on SEEK
-----Inline Attachment Follows-----
------------------------------------------------------------------------------
-----Inline Attachment Follows-----
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
------------------------------------------------------------------------------
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
