As a developer who would like to eventually develop core code in Lucene (I started but then things changed drastically and so will wait for flexible indexing and other APIs?), a standard logging system would make development easier by making debugging easier. I rely heavily on log analysis in developing and debugging search code. A detailed view of what is happening internally will speed development, and as Shai mentioned allow production and pre-production systems to be monitored in new ways.
-J On Fri, Dec 5, 2008 at 1:19 PM, Doug Cutting <[EMAIL PROTECTED]> wrote: > John Wang wrote: > >> If we were to depend on a jar for logging, then why not log4j or >> commons-logging? >> > > Lucene is used by many applications. Many of those applications already > perform some kind of logging. We'd like whatever Lucene adds to fit in with > their existing logging framework, not conflict with it. Thus the motivation > to use a meta-logging framwork like commons logging or slf4j. And articles > like the following point towards slf4j, not commons logging. > > http://www.qos.ch/logging/thinkAgain.jsp > > > Doug > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
