[
https://issues.apache.org/jira/browse/SOLR-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062004#comment-13062004
]
Robert Muir commented on SOLR-2616:
-----------------------------------
{quote}
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.
{quote}
yeah as long as we dont somehow create test meddling, I'm happy! There is
already some hacks in the build somehow related to this:
{noformat}
in lucene/common-build.xml: <property name="tests.loggingfile"
value="/dev/null"/>
and in the JUnitResultFormatter to reboot logging for each test case:
try {
LogManager.getLogManager().readConfiguration();
} catch (Exception e) {}
{noformat}
> 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: [email protected]
For additional commands, e-mail: [email protected]
