Gary Gregory wrote: > Then there are questions like: should the "memory log" really be in CL > as opposed to logj4?
Well, see the focus of the class. It targets especially unit tests in combination with coverage tools. Personally I can live perfectly with the jdk logger (unless someone wants more sophisticated possibilities and is willing to pay the price in the increased project size for L4J). CL allows me to use the most lightweight implementation during development and using the MemoryLogger I can assure, that the logger code does not have impact on runtime behaviour (still using CL). -- J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
