Ideas...

 

1.      Set resultpropert and set failonerror to false. This way you can see 
what errorcode was returned and that may give you a hint. 
2.      Are there any environmental variables that need to be set for it to 
work? Perhaps you need to set them.
3.      Try setting useruntimeengine to true. I could never find good docs on 
what this did, but sometimes it helps. I think it has to do with if a new cmd 
process is opened or not.

 

BOb

 

 

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Mitchell
Sent: Monday, May 05, 2008 5:23 PM
To: [EMAIL PROTECTED]
Subject: Re: [NAnt-users] Exec command

 


Hi Bob,


Yes I have verbose on, here is my exact command.


<exec program="${project.installer.build.exe}" 
basedir="${project.installer.base.dir}"


                        failonerror="false" verbose="${project.verbose}" >


                        <arg value="${project.installer.file}" />


                        <arg line="-nowait" />


            </exec>


Like I said it gets about half way through the installer build, before it goes 
belly up. The working directory is being set correctly, that was the first 
thing I checked. Oh yeah, and verbose is set to true, and I can see it 
compressing he files until all the sudden it stops. 


 


Thanks,


Scott Mitchell


 


Re: [NAnt-users] Exec command


Bob Archer
Mon, 05 May 2008 13:13:36 -0700

Did you try setting verbose to true to see what was happening? Perhaps it is 
not running in the directory you are expecting? Try setting the working 
directory to the directory you are in when you run it from the command line. A 
lot of times that is my trouble when EXEC doesn't work.
 
 
 
BOb
 
 
 
 
 
________________________________
 
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Scott Mitchell
Sent: Monday, May 05, 2008 4:08 PM
To: [EMAIL PROTECTED]
Subject: [NAnt-users] Exec command
 
 
 
I am having a problem with the <exec> command. (I think it is the <exec> 
command at least)
 
 
 
I have started switching our build system to use NANT for the building of our 
software. It is going very good, and has replaced so much of our old Perl 
scripts, with relative ease. The problem I have run into is building our 
installer .exe. We use Ghost Installer, and this has been working with our Perl 
scripts by just calling it in a system() call with the command line. Now I can 
also run this installer builder from the command line with out any problems. 
But when I try to run this command line form the <exec> command it makes it 
through about ½ way building the actual installer and then it comes back with 
and "unknown error" and does not build the installer. But like I said the weird 
thing is I can run this from the command line and through the Ghost Installer 
Builder and build the installer without problems, but when using <exec> , it 
almost always fail. I have also as a test put the command line call in a .bat 
file, and tried calling the .bat file form the <exec> command but I run in to 
the same problem still. I know this is not much to go on, I just thought I 
would ask here to see if this sounds like anything anyone else has experienced. 
 
 
 
Thanks in advance for any help.
 
 
 
Scott Mitchell
 
 
 
--
 
Scott Mitchell
 
Engineering
 
 
 
Colorado vNet
 
 
 
direct 970 203 3756
 
main 970 203 3700
 
fax 970 203 3701
 
 
 
email [EMAIL PROTECTED] <[EMAIL PROTECTED]> 
 
web www.coloradovnet.com <http://www.coloradovnet.com> 
 
 
 
255 East Sixth Street
 
Loveland, Colorado 80537
 
 
 
 
 

 

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to