[
https://issues.apache.org/jira/browse/SOLR-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976143#action_12976143
]
Hoss Man commented on SOLR-2303:
--------------------------------
I think the purpose of the log4j-over-slf4j jars was so that the third party
jars included in solr (and in contribs) which use log4j logging will have all
of their messages funneled through slf4j so all logging for "basic" solr users
will be consistent (JUL) -- if you remove it, some solr logging will use
slf4j->JUL and some will go direct to log4j.
I *think* the other log4j jars you mentioned (contrib/extraction,
contrib/clustering) are the ones that should be removed. (untested that this
doesn't break anything)
> remove unnecessary (and problematic) log4j jars in contribs
> -----------------------------------------------------------
>
> Key: SOLR-2303
> URL: https://issues.apache.org/jira/browse/SOLR-2303
> Project: Solr
> Issue Type: Improvement
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
> Attachments: SOLR-2303.patch
>
>
> In solr 4.0 there is log4j-over-slf4j.
> But if you have log4j jars also in the classpath (e.g. contrib/extraction,
> contrib/clustering) you can get strange errors such as:
> java.lang.NoSuchMethodError: org.apache.log4j.Logger.setAdditivity(Z)V
> So I think we should remove the log4j jars in these contribs, all tests pass
> with them removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
