Hi Jukka, I think that we need to standardize on the underlying logging library in the core Tika code. I'm actually a fan of JDK's logging facilities, however, I'm open to other options as well.
It's going to be difficult to control the underlying log libraries used by external parsing plugins, agreed, however that's partially a function of how the external library is called (e.g., if it's called through a Runtime.getRuntime().exec(), then we'll have little programmatic control of the external log library, versus if it's called programmatically, and has Java APIs). In any case, my +1 for JDK logging. Thanks, Chris On 10/5/07 9:13 AM, "Jukka Zitting" <[EMAIL PROTECTED]> wrote: > Hi, > > Any thoughts on logging within Tika components? We already have both > commons-logging and log4j as dependencies, and I wouldn't be surprised > to see some external parser libraries using JUL or SLF4J for logging. > > See also http://kasparov.skife.org/blog/src/logging_for_libraries.html > > BR, > > Jukka Zitting ______________________________________________ Chris Mattmann, Ph.D. [EMAIL PROTECTED] Cognizant Development Engineer Early Detection Research Network Project _________________________________________________ Jet Propulsion Laboratory Pasadena, CA Office: 171-266B Mailstop: 171-246 _______________________________________________________ Disclaimer: The opinions presented within are my own and do not reflect those of either NASA, JPL, or the California Institute of Technology.
