On 30 May 2003 at 14:15, Jeremy Arnold wrote: > Hello, > [snip] > For making changes to the call to getLoggerFor( ) for all of the > classes, it might be easier for one of the committers to do this > directly, rather than dealing with patches.
That's very true. -Mike > > BAZLEY, Sebastian wrote: > > >Yes, thanks, agreed - that would simplify/rationalise the logging using > >Avalon logkit. > > > >But it would not allow the use of LOG4J or Java 1.4 logging without > >edit/recompile, AFAIK. > >For most source files, the changes to convert to Commons Logging would be > >very similar to those needed to tidy up the logging categories, which is why > >I thought it might be useful to consider. > > > >But I am happy to stick with LogKit if everyone else is. > >[One could always do the Commons Logging change later - it would be simple > >using Eclipse!] > > > >I would like to be able to change the logging level without having to edit > >the properties file. > >I can contribute a patch to add a command line option to do this (calling > >the LoggingManager method). > > > >I'll try and get some patches out this weekend. > > > >The changes to getLoggerFor() could be done as one or more patch files - > >which is easiest for the commiters? > >One giant patch, one per file, or perhaps one per functional area (core, > >protocol etc)? > > > >By the way, LoggingManager seems to be in jorphan.jar, which strikes me as a > >bit odd. > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 AIM: mstover777 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
