Leo Sutic wrote:
*snip* > I'm calling a vote: > > Should the class org.apache.avalon.framework.logger.ConsoleLogger, as I > implemented it, go into Avalon/Framework? > > My argument for it: > Sometimes it is impractical or impossible to obtain a logger. However, > in almost all cases the application has access to System.out. A > ConsoleLogger is a replacement for inserting System.out.println into > the code and brings higher code quality. > > The ConsoleLogger belongs in framework. Framework consists of > interfaces and basic implementations of them. NullLogger and > ConsoleLogger gives us: > > no logging: NullLogger > simplest possible logging: ConsoleLogger > (everything else: LogKit / Log4J / JDK1.4) > > So we have the null object pattern in NullLogger, and the > simplest possible working implementation in ConsoleLogger. > > END OF VOTE ------------------------------------------------------- +1 with note that I think the default logging level should ERROR not DEBUG. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
