[ 
https://issues.apache.org/jira/browse/SOLR-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311153#comment-15311153
 ] 

Shawn Heisey edited comment on SOLR-7887 at 6/1/16 9:31 PM:
------------------------------------------------------------

I suspect that if you add log4j-jcl, commons-logging, log4j-1.2-api, and 
log4j-jul, you'll cover the three logging libraries which are used by 
dependencies.

The information on the runtime dependency page says that log4j-jcl requires 
commons logging ... which seems odd, because I would have expected it to 
*implement* commons logging like jcl-over-slf4j (which is in the stock lib/ext 
directory) does.

Edit:  I just noticed that you mentioned log4j-1.2-api already, and that it 
didn't work.  I am not sure what to say about that.


was (Author: elyograg):
I suspect that if you add log4j-jcl, commons-logging, log4j-1.2-api, and 
log4j-jul, you'll cover the three logging libraries which are used by 
dependencies.

The information on the runtime dependency page says that log4j-jcl requires 
commons logging ... which seems odd, because I would have expected it to 
*implement* commons logging like jcl-over-slf4j (which is in the stock lib/ext 
directory) does.


> Upgrade Solr to use log4j2 -- log4j 1 now officially end of life
> ----------------------------------------------------------------
>
>                 Key: SOLR-7887
>                 URL: https://issues.apache.org/jira/browse/SOLR-7887
>             Project: Solr
>          Issue Type: Task
>    Affects Versions: 5.2.1
>            Reporter: Shawn Heisey
>         Attachments: SOLR-7887-WIP.patch
>
>
> The logging services project has officially announced the EOL of log4j 1:
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> In the official binary jetty deployment, we use use log4j 1.2 as our final 
> logging destination, so the admin UI has a log watcher that actually uses 
> log4j and java.util.logging classes.  That will need to be extended to add 
> log4j2.  I think that might be the largest pain point to this upgrade.
> There is some crossover between log4j2 and slf4j.  Figuring out exactly which 
> jars need to be in the lib/ext directory will take some research.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to