Hi Costin (and Remy),

I had a quick look at the JdkLoggerFormatter (found in an old revision of the sandbox, it's not there any more):

this formatter uses a *very* compact format. E.g. the timestamp is just the milliseconds and the log level is abbreviated with a single character. Although technically very useful, I doubt that most admins will like it at first sight, so it might not be a good default replacement for the JDK simple formatter. Still searching ...

Regards,

Rainer

Costin Manolache wrote:
I think something is missing - DirectJDKLog is looking for a
JdkLoggerFormatter that would do
the trick. I may have forgot to add it, I have it on my machine ( I hate too
the default format ).
There's also a config override allowing default properties to be loaded from
a different location.

Costin

On 8/2/07, Remy Maucherat <[EMAIL PROTECTED]> wrote:
Rainer Jung wrote:
That's why it would be nice if someone took the burden of writing a
better log formatter for j.u.l.
Got it.  Yea, that format is certainly grep unfriendly.

Looks like Harmony has a formatter we could copy from and fix to not
add the new line.


http://svn.apache.org/repos/asf/harmony/enhanced/classlib/trunk/modules/logging/src/main/java/java/util/logging/SimpleFormatter.java
Yes, that could be a good starting point (although that implementation
does not care about localization).
It might be better to use log4j code as a starting point as it already
has the pattern processing code.

Rémy

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to