lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Reopened] (SOLR-3706) Ship setup to log with log4j.
Date Wed, 27 Mar 2013 23:07:15 GMT


Hoss Man reopened SOLR-3706:

Something is still broken as far as how log4j is being configured when tests are run...

hossman@frisbee:~/lucene/dev/solr/solrj$ ant test -Dtestcase=SolrExampleXMLTest
[junit4:junit4] <JUnit4> says hi! Master seed: 7C26743BA1BE32C5
[junit4:junit4] Executing 1 suite with 1 JVM.
[junit4:junit4] Started J0 PID(6428@frisbee).
[junit4:junit4] Suite: org.apache.solr.client.solrj.SolrExampleXMLTest
[junit4:junit4]   2> SLF4J: Class path contains multiple SLF4J bindings.
[junit4:junit4]   2> SLF4J: Found binding in [jar:file:/home/hossman/lucene/dev/solr/solrj/lib/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[junit4:junit4]   2> SLF4J: Found binding in [jar:file:/home/hossman/lucene/dev/solr/core/lib/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[junit4:junit4]   2> SLF4J: Found binding in [jar:file:/home/hossman/lucene/dev/solr/example/lib/ext/slf4j-log4j12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[junit4:junit4]   2> SLF4J: See for an
[junit4:junit4]   2> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
[junit4:junit4]   2> log4j:WARN No appenders could be found for logger (org.apache.solr.SolrJettyTestBase).
[junit4:junit4]   2> log4j:WARN Please initialize the log4j system properly.
[junit4:junit4]   2> log4j:WARN See
for more info.
> 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-maven.patch, SOLR-3706-maven.patch, SOLR-3706.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