[
https://issues.apache.org/jira/browse/SOLR-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028283#comment-13028283
]
Hoss Man commented on SOLR-2487:
--------------------------------
bq. 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.
Personally, that sounds like a terrible idea to me.
Novice users would try the demo, see that it works, then try deploying to some
other servlet container and suddenly get errors unless the servlet container
had already explicitly loaded some slf4j binding jar?
we already have plenty of users who get confused about how (and even *why*)
they configure the solr home dir when deploying solr to a servlet container --
this would make it ever harder for beginners.
simple things should be simple -- novice users should be able to copy a jar,
and copy configs, and be good to go.
for a user who cares about jdk14 logging vs log4j vs whatever, the task of
customizing the war is simple and straightforward to understand -- but for a
solr user who doesn't know anything about java, picking an slf4j binding and
configuring their servlet container to load could easily appear like a daunting
burden that will make them turn away from even using solr past the tutorial
stage.
this really seems like a no brainer to me
> 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
