I actually didn't think about this immediately, but adding zip support to the MailLogger would add a dependency for #ziplib to NAnt.Core, and I'm not sure if we want that ...
Ian and Scott, what do you think ? Gert ----- Original Message ----- From: "Nicklas Norling" <[EMAIL PROTECTED]> To: "'Gert Driesen'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, October 15, 2003 5:01 PM Subject: RE: [Nant-users] Logging failures or successes > Hi Gert. > > Thanks for the input! Time to get my hands dirty then :) > Can't promise anything, but I'll certainly look into > doing such patches (if I can). > /Nicke > > -----Original Message----- > From: Gert Driesen [mailto:[EMAIL PROTECTED] > Sent: den 15 oktober 2003 16:56 > To: Nicklas Norling; [EMAIL PROTECTED] > Subject: Re: [Nant-users] Logging failures or successes > > > ----- Original Message ----- > From: "Nicklas Norling" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, October 15, 2003 4:43 PM > Subject: [Nant-users] Logging failures or successes > > > > Hi all. > > > > I'm building a number of projects and would like to send > > out feedback from the build using email. > > Unfortunately the logs get big and I must zip the logs > > before sending them in email. I've understood that leaves > > me with the <mail> task. (NAnt.Core.MailLogger has no compression). > > > > When the build is going ok, I want to send a short notice about the > > happy occasion. > > > > When the build goes wrong I want to zip up all the logs > > and email them to my user list using the <zip> and <mail> tasks. > > > > The problem is that in order to know if the build succeeded or not, I > > must be using nant.onsuccess/nant.onfailure. And that means I must be > > executing in the same script as the build when I jump off to send > > feedback. But the log files are then locked and can not be zipped. > > > > <command> > > C:\Harv>nant -nologo -f:main.build -l:FullBuild.log all </command> > > <result> > > ..... > > ziplogs: > > > > [zip] Zipping 4 files to C:\Harv\BuildLogs.zip. > > C:\Harv\main.build(65,6): > > Zip file 'C:\Harv\BuildLogs.zip' could not be created. > > The process cannot access the file "C:\Harv\FullBuild.log" because > > it is being used by another process. </result> > > > > If I on the other hand where to run a separate nant after the build, > > then the log file is not locked, but I don't have the information > > about the success/failure of the build. > > > > How would one go about solving such a thing? > > > I would suggest posting a patch that would : > > - add an option to the MailLogger to send the build log as an attachment > - add another option to have it zip the build log (if its to be send as an > attachment only ofcourse) > > Thanks, > > Gert > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > SourceForge.net hosts over 70,000 Open Source Projects. > See the people who have HELPED US provide better services: > Click here: http://sourceforge.net/supporters.php > _______________________________________________ > Nant-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-users > > ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
