[
https://issues.apache.org/jira/browse/SOLR-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036812#comment-13036812
]
Jan Høydahl commented on SOLR-2487:
-----------------------------------
Poll results from solr-user:
{code}
[3] I always use the JDK logging as bundled in solr.war, that's perfect
[6] I sometimes use log4j or another framework and am happy with re-packaging
solr.war
[5] Give me solr.war WITHOUT an slf4j logger binding, so I can choose at
deploy time
[4] Let me choose whether to bundle a binding or not at build time, using an
ANT option
[1] What's wrong with the "solr/example" Jetty? I never run Solr elsewhere!
[ ] What? Solr can do logging? How cool!
[1] Please, better logging documentation!
{code}
> Do not include slf4j-jdk14 jar in WAR
> -------------------------------------
>
> Key: SOLR-2487
> URL: https://issues.apache.org/jira/browse/SOLR-2487
> Project: Solr
> Issue Type: Improvement
> Components: Build
> Affects Versions: 3.2, 4.0
> Reporter: Jan Høydahl
> Labels: logging, slf4j
>
> I know we've intentionally bundled slf4j-jdk14-1.5.5.jar in the war to help
> newbies get up and running. But I find myself re-packaging the war for every
> customer when adapting to their choice of logger framework, which is
> counter-productive.
> It would be sufficient to have the jdk-logging binding in example/lib to let
> the example and tutorial still work OOTB but as soon as you deploy solr.war
> to production you're forced to explicitly decide what logging to use.
--
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
