[
https://issues.apache.org/jira/browse/SOLR-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028300#comment-13028300
]
Jan Høydahl commented on SOLR-2487:
-----------------------------------
@Hoss
Your concerns are easily solved by documentation.
The novice users you're talking about are not likely to ever move past running
Solr from the included Jetty in the example folder (I've seen such people).
When you get to deploying to another servlet container, then you already know
what a Java servlet container is. You also know about Java logging, setting
Java Opts, and most importantly you read the install docs and understand how to
copy a jar file into a folder.
SLF4j is now so common that the issue of having multiple crashing SLF4j
bindings in your classpath will be more annoying to novice users than the
opposite.
>From version 1.6 SLF4j will default to NOP binding if no binding is found, so
>users will still be able to use Solr:
>http://www.slf4j.org/codes.html#StaticLoggerBinder
> 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
