[
https://issues.apache.org/jira/browse/SOLR-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616005#comment-13616005
]
Mark Miller commented on SOLR-3706:
-----------------------------------
Between the one run i saw fail locally and your stuff above, it looks like just
example based tests. And we have the jars both in the example and in solrj and
in core (hence the warnings, though they never caused me any grief in my
testing before). Not sure how to get around that (or if it is indeed the
problem).
> Ship setup to log with log4j.
> -----------------------------
>
> Key: SOLR-3706
> URL: https://issues.apache.org/jira/browse/SOLR-3706
> 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, 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, etc.
> If someone wants to use JUL they still can - but at least users could start
> with something decent.
--
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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
