http://bugzilla.wpkg.org/show_bug.cgi?id=79 Rainer Meier <skybeam at users.sourceforge.net> changed: What |Removed |Added Attachment #47 is|0 |1 obsolete| | --- Comment #7 from Rainer Meier <skybeam at users.sourceforge.net> 2007-11-05 23:55:32 --- Created an attachment (id=48) --> (http://bugzilla.wpkg.org/attachment.cgi?id=48) Updates and fixes as requested. Merged with v.0.9.12-test3 As requested the fixes from 0.9.12-test3 have been merged. Additionally added the ability to use the applying profile within the log file pattern by using the [PROFILE] placeholder. Unfortunately this causes some problems since the profile is not available since the script startup but just a bit later. As a work-around all output produced before profiles.xml is read is written to the local %TEMP% folder (which are just a few debug messages). Here's a list of changes/fixes: * FIX: Usage of [PROFILE] tag was described within the /logfilePattern * documentation but not implemented. Added implementation. * FIX: Temporary log file at WPKG startup (written to %TEMP%) is now properly * closed. * FIX: Modified regular expression to replace CR/LF with pipes for logfile * output (was matching LF only before). * FIX: Log file timestamp now contains log severity. * MOD: Error in case of failed XML file read is now printed in one message * instead of splitting it to several event log entries. * MOD: Debug output is not any more coupled with logLevel. A log level of 16 * will log debug output even if /debug is not set. This allows running * the script on clients with default log level while writing a debug * log file to the log directory. This is handy to prevent polluting the * client event log with wpkg messages. * MOD: Integraded changes from version 0.9.12-test 3: * - config.xml is now optional. * - Bug 75: Failed to check file revision could not be retrieved. * MOD: Optimized getProfile(), caching value now instead of re-evaluating * on each call. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. wpkg-users mailing list wpkg-users at lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users |