I recently upgraded from clover 2.8 to 3.0 and I can’t seem to control the logging. Everything is printed to System.err and there’s extraneous lines in the debug output w/ the date & context of the debug:
Aug 25, 2010 12:43:12 PM org.jetel.data.Defaults openResourceStream
INFO: Loading default properties from: defaultProperties
Aug 25, 2010 12:43:12 PM org.jetel.graph.runtime.EngineInitializer initGraph
INFO: Checking graph configuration...
Aug 25, 2010 12:43:12 PM org.jetel.graph.runtime.EngineInitializer initGraph
INFO: Graph configuration is valid.
Ideally, this output would be:
INFO: Loading default properties from: defaultProperties
INFO: Checking graph configuration...
INFO: Graph configuration is valid.
The extra stuff isn’t as much of an issue as the fact I can’t seem to control any of the clover logging, I can’t alter it, I can’t disable it, I can’t get it to pipe to a file.
I unjarred the cloveretl.engine.jar and removed the log4j.properties from there and that did not affect anything. I’ve been trying to override this behavior in my own local log4j properties, but that isn’t affecting it either.
One of the libraries I use along w/ clover uses slf4j, my client uses plain old log4j, and as I understand it clover is using commons logging, could there be some sort of weird interaction here?
I’m sure I’m missing something obvious, but it’s not jumping out at me. Any thoughts?
Thanks.