Here are some notes on what I was thinking. I did a bit of research and found that the results in this sample program pretty good. I thought that it would be a perfect place for using Events but it turned out to cause more trouble than it was worth.
The BuildLog.cs was the version that I was finally happy with. If we added a Log.WriteLine method it shouldn't break existing Task code which would be nice. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 18, 2002 3:44 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] XML Logging? Ian: >I think that 1 or 2 are the better options with 2 being the cleanest >but the most work. I haven't looked at Ants logging system to be sure >though. Thanks for the feedback Ian. I've only looked at Ant 1.5's documentation, not the code but they have loggers and listeners and log events (start/end build/task/target etc.) >1) Change the logging so that it produces unformatted text, and then a >formatter that produces the console style (or xml) output ( a lot of >work) >2) Implement a logging system like Ant's that has log events, and allow the >logger to handle those events as makes sense (even more work) Has anyone looked into the effort of doing this? Has there been any discussion or thoughts about how it should go? I am already gearing up for a nice refactoring/spike session, so I'll let you know how it turns out -- looks like no sleep tonight :-) Best, Bill ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Log.zip
Description: Binary data
