lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McKinley (JIRA)" <>
Subject [jira] [Commented] (SOLR-3706) Ship setup to log with log4j.
Date Fri, 22 Mar 2013 04:55:16 GMT


Ryan McKinley commented on SOLR-3706:

My question was only about the slf4j-api.jar file *not* any of the implementation jars

If we don't include the -api.jar and there is no logging configured in the container it will
crash with a ClassNotFound exception.  If we add the -api.jar file it will write a line to
stdout and stderr that say "no logging framework found" and then hide all logging messages.
 (this is the default slf4j behavior)

> Ship setup to log with log4j.
> -----------------------------
>                 Key: SOLR-3706
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: 4.3, 5.0
>         Attachments: SOLR-3706.patch, SOLR-3706-solr-log4j.patch, SOLR-3706-solr-log4j.patch
> Currently we default to java util logging and it's terrible in my opinion.
> *It's simple built in logger is a 2 line logger.
> *You have to jump through hoops to use your own custom formatter with jetty - either
putting your class in the start.jar or other pain in the butt solutions.
> *It can't roll files by date out of the box.
> I'm sure there are more issues, but those are the ones annoying me now. We should switch
to log4j - it's much nicer and it's easy to get a nice single line format and roll by date,
> If someone wants to use JUL they still can - but at least users could start with something

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message