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 3419DD3CA for ; Fri, 15 Mar 2013 17:00:20 +0000 (UTC) Received: (qmail 22302 invoked by uid 500); 15 Mar 2013 17:00:17 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 22231 invoked by uid 500); 15 Mar 2013 17:00:17 -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 22123 invoked by uid 99); 15 Mar 2013 17:00:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Mar 2013 17:00:17 +0000 Date: Fri, 15 Mar 2013 17:00:16 +0000 (UTC) From: "Mark Miller (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=13603517#comment-13603517 ] Mark Miller commented on SOLR-3706: ----------------------------------- bq. but last we discussed inertia pointed towords keeping concrete logging dependencies in solr.war Why? I don't see anyone arguing for that here. There seems to be plenty of advantageous to getting it out of the webapp and plenty of downsides to having it in. Where and what is someone else arguing? > 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-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