[
https://issues.apache.org/jira/browse/LOG4J2-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15744853#comment-15744853
]
Greg Thomas commented on LOG4J2-1473:
-------------------------------------
I've just started using the Apache LDAP client API, part of the Apache
Directory project - http://directory.apache.org/
The client API (and presumably other components of Apache Directory) are using
SLF4J.
It's not strictly an upgrade from Log4j1 so perhaps not part of this parent
JIRA, but I'd like to think it would be an upgrade to move to Log4j2. Should
Apache Directory be added as a sub-task ?
> Inform other Apache projects using Log4j 1.x that it won't be supported in
> JDK9
> -------------------------------------------------------------------------------
>
> Key: LOG4J2-1473
> URL: https://issues.apache.org/jira/browse/LOG4J2-1473
> Project: Log4j 2
> Issue Type: Umbrella
> Reporter: Matt Sicker
>
> Due to various issues in Log4j 1.2.x, it will no longer work in JDK9:
> http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008654.html
> As Log4j 1.x is EOL, we are not adding new updates, so Apache projects that
> are using Log4j 1.x still should be informed of the pending issues. We can
> offer help to upgrade to Log4j 2.x.
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> This issue is a collector for the various projects that are still using Log4j
> 1.x. Each project should be made into a subtask of this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
