> ----- Original Message ----- > From: "Troy Laurin" <[EMAIL PROTECTED]> > To: "Nant-Developers (E-Mail)" <[EMAIL PROTECTED]> > Sent: Monday, July 19, 2004 4:55 AM > Subject: [nant-dev] XmlLogger is broken? >
> I'm having an issue with using XmlLogger in my build... > > In particular, registering NAnt.Core.XmlLogger as a build listener > causes my build to fail and hang, part-way through. I suspect that the > logger's buffer is getting full (?), since the build hangs in different > (but consistent) places depending on what build elements are included. > Our build is rather noisy... The xml file that is found when the build > hangs is close to 4M in size... but this in itself is confusing, because > I understood that the xml log file isn't written until the build is > complete? Yes, that is correct. This used to be different though. What version of NAnt are you using ? > > > Which brings up the question... why isn't the xml log streamed to file? The reason for this was to make the XmlLogger serializable, which is necessary if we want to support logging in other than the default appdomain (unless someone has a solution for this). > Logs are most useful when they are immediately available - if the build > is terminated uncleanly (power failure, or malicious kill command) then > the log-to-date can still be used, but if the log is buffered at all, > then potentially valuable information can be (will probably be) lost. I agree, please feel free to propose (provide) a better solution that still allows the XmlLogger to be serialized ... Gert ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
