[
https://issues.apache.org/jira/browse/SOLR-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591672#action_12591672
]
Ryan McKinley commented on SOLR-549:
------------------------------------
This solves the "how do I use log4j in solr" problem, but I think it sends solr
down the wrong path. I really don't think we want to deal with configuring the
logging internally. That is what the logging frameworks are supposed to do for
us!
Rather then taking this approach, I think we should just use SLF4J
(http://www.slf4j.org/), it does what this patch does, but it is supported
elsewhere and has more options ;)
> Enable configurable logging (jul or log4j)
> ------------------------------------------
>
> Key: SOLR-549
> URL: https://issues.apache.org/jira/browse/SOLR-549
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Henri Biestro
> Attachments: solr-log4j.patch
>
>
> java.util.logging does not allow to easily create a self-sufficient 'war'
> with respect to logging configuration.
> The java.util.logging.LogManager used by the application is always created by
> the container and is thus only configurable through the container;
> furthermore, if one already uses say log4j in a webapp that embeds Solr, it
> does not even seem possible to re-route jul logging into log4j just by
> configuration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
