Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 86DDFFA7B for ; Fri, 22 Mar 2013 04:41:18 +0000 (UTC) Received: (qmail 15372 invoked by uid 500); 22 Mar 2013 04:41:17 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 14991 invoked by uid 500); 22 Mar 2013 04:41:16 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 14934 invoked by uid 99); 22 Mar 2013 04:41:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Mar 2013 04:41:15 +0000 Date: Fri, 22 Mar 2013 04:41:15 +0000 (UTC) From: "David Smiley (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SOLR-3706) Ship setup to log with log4j. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609914#comment-13609914 ] David Smiley commented on SOLR-3706: ------------------------------------ As long it's _also_ easy to handle an SLF4J-less war in Tomcat, then I think it's fine too. Nonetheless this is going to be a new thing a deployer of Solr needs to check the box in their checklist. It might be a good idea to have a very early classloader check in SolrDispatchFilter that checks if SLF4J is there and if not then gives you a very helpful message to remedy it -- i.e. you need to place SLF4J jars in your app-server somewhere or re-pack the WAR with them. > 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.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: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org