[
https://issues.apache.org/jira/browse/SOLR-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591680#action_12591680
]
Henri Biestro commented on SOLR-549:
------------------------------------
I agree on all terms; it only solves the "how do I use log4j in solr" and as as
such is definitely not as feature-full nor as generic as slf4j.
I also agree that the logging configuration issue is not something that Solr
can or should take care of; and I'm not suggesting that we try. I'm just
seeking a way to open a door so logging is a choice that can be configured &
packaged easily.
The only plus of the patch is that it avoids adding a hard library-dependency
(whether on slf4j or log4j) which seemed to be one the blockers in past threads.
If this constraint is relaxed, let's by all means use slf4j and be done!
> 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.
