[
https://issues.apache.org/jira/browse/SOLR-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126844#comment-13126844
]
Hoss Man commented on SOLR-2487:
--------------------------------
David: I don't really understand what you mean by "adding an expanded WAR
deployment option" ... nothing in the solr build system handles "deployment" we
just generate artifacts, and one of those artifacts is a war - if you want to
expand that war (to customize it) it's trivial to run "jar xf solr.war"
> 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
> Attachments: SOLR-2487.patch
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
