[
https://issues.apache.org/jira/browse/SOLR-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300958#comment-16300958
]
Ralph Goers edited comment on SOLR-7887 at 12/22/17 4:53 AM:
-------------------------------------------------------------
Log4j 2.10.0 provides AppenderSkeleton in the log4j-1.2-api jar. I verified
that it solves the Hadoop issue when I migrated Flume to Log4j 2. Also, I was
informed that the reason Oracle closed the issue with doclint as they consider
there to be workarounds - either don't use doclint or disable annotation
processing. If you have no custom Log4j plugins and no other need for
annotation processing you can disable it.
was (Author: [email protected]):
Log4j 2.10.0 provides AppenderSkeleton in the log4j-1.2-api jar. I verified
that it solves the Hadoop issue when I migrated Flume to Log4j 2.
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
