It would be relatively easily to write a Formatter class that takes a string suitable for use with MessageFormat, and then configure that and its pattern in a config file. Maybe 20 lines of code. But yeah I don't know of something out of the box.
I suppose the idea is that the -jcl or -log4j dependency is only needed at runtime to bind to your preferred logging system. You can and should change it according to your taste. Should you check in that change? I imagine most people won't configure the logger, so don't care. I think we picked JCL as the default destination since other dependencies log straight to JCL. I suppose that represents my only concern, then, that we could be forcing people to configure 2 systems this way. Could you just keep the change local? On Fri, Feb 12, 2010 at 3:43 AM, Drew Farris <drew.far...@gmail.com> wrote: > Hi All, > > java.util.logging is really getting me down - I never really paid much > attention to it because I've always used log4j in the past, but it > looks like it can't do things like change the format of the logs using > a config file, do mapped diagnostic contextes, etc.. > > Does anyone have any issue with adding log4j as a dependency and using > it to configure log output via slf4j-jcl? (commons logging > auto-configures itself to use log4j as long as the jar is in the > classpath). I know we're trying to trim out dependencies, but in this > case I think it's useful, at least in the context of the command-line > utilities. I don't think it needs to be in the job files. > > Drew >
