[
https://issues.apache.org/jira/browse/SOLR-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062000#comment-13062000
]
Mark Miller commented on SOLR-2616:
-----------------------------------
bq. The logging configuration file I provided does not log to a file nor does
it suppress logging to the console.
The question in my mind is not what the patch does, but what should we do.
If we want this as an example that is not hooked up, my preference would be to
let the user know he should use -D to hook up the sample log file - not
configure it in jetty.xml - we should still stay somewhat logging framework
agnostic.
In both cases I would prefer that the default log.properties file use the
FileHandler rather than ConsoleHandler though. We should give something close
to what you actually might want to use - which is not to setup logging to log
to the console.
First I'm gathering feedback from others though.
My current leaning is to doc the wiki and what not to mention the sample log
props and use of -D to put it in action, and to setup the default log props to
log to the ./logs dir.
> Include jdk14 logging configuration file
> ----------------------------------------
>
> Key: SOLR-2616
> URL: https://issues.apache.org/jira/browse/SOLR-2616
> Project: Solr
> Issue Type: Improvement
> Reporter: David Smiley
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 3.4, 4.0
>
> Attachments: SOLR-2616_jdk14logging_setup.patch
>
>
> The /example/ Jetty Solr configuration should include a basic logging
> configuration file. Looking at this wiki page:
> http://wiki.apache.org/solr/LoggingInDefaultJettySetup I am creating this
> patch.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
