That is a good plan. We marked it as deprecated as a warning, but it will not
be removed in a 2.x release.
Ralph
> On Feb 24, 2023, at 1:44 PM, Kish, Robert [AG]
> wrote:
>
> Thanks for the responses! I won't worry about having to change my code /
> environment setup now and will instead
Thanks for the responses! I won't worry about having to change my code /
environment setup now and will instead ignore the deprecation warning and wait
for the eventual 3.0 release.
-Original Message-
From: Ralph Goers
Sent: Friday, February 24, 2023 03:40 PM
To: Log4J Users List
Note - the annotation processor will still be required in 3.0. Instead of
generating a Log4jplugins.dat file it generates a Java class file. That class
file is loaded via the ServliceLoader.
Also, Log4j 3 requires Java 11 and supports JPMS. With JPMS applications have
to specify the
We’re removing it in 3.0. In 3.0, plugins are instead loaded via ServiceLoader
from the JDK. The annotation processor was updated to generate the service
classes with the plugin metadata, though that can be created manually if
necessary. This is related to supporting Java modules which don’t
I see with version 2.20 that plugin package scanning is now marked for
deprecation. This sounds great except for my use case of running a Tomcat web
application inside of Eclipse. Eclipse compiles the code itself and launches
Tomcat for ease of development. But this internal compiler has no
