[
https://issues.apache.org/jira/browse/SOLR-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198147#comment-16198147
]
Ralph Goers edited comment on SOLR-7887 at 10/10/17 4:33 AM:
-------------------------------------------------------------
If you need it, Log4j 2 could look into implementing AppenderSkeleton but it
most likely would end up being a no-op so Hadoop's Appender might not do
anything. That almost certainly doesn't matter since the appender would never
be called by Log4j 2. If you can create a Log4j 2 Jira issue that identifies
what Hadoop is trying to do perhaps we can find a way to accommodate it.
Also, please note that the doclint error was captured in
https://issues.apache.org/jira/browse/LOG4J2-1925. It is caused by a bug in
javac as documented in
http://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8186647. Oracle has
closed it as won't fix. The problem does not occur in Java 9.
was (Author: [email protected]):
If you need it, Log4j 2 could look into implementing AppenderSkeleton but it
most likely would end up being a no-op so Hadoop's Appender might not do
anything. If you can create a Log4j 2 Jira issue that identifies what Hadoop is
trying to do perhaps we can find a way to accommodate it.
Also, please note that the doclint error was captured in
https://issues.apache.org/jira/browse/LOG4J2-1925. It is caused by a bug in
javac as documented in
http://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8186647. Oracle has
closed it as won't fix. The problem does not occur in Java 9.
> 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]
