Ralph Goers created LOG4J2-3644:
-----------------------------------

             Summary: Deprecate package scanning in 2.x and remove in 3.0
                 Key: LOG4J2-3644
                 URL: https://issues.apache.org/jira/browse/LOG4J2-3644
             Project: Log4j 2
          Issue Type: Task
          Components: Plugins
    Affects Versions: 2.19.0
            Reporter: Ralph Goers
             Fix For: 2.19.1


Package scanning is been discouraged since the Log4j 2 annotation processor was 
first created. Users who use it typically either aren't aware it isn't 
necessary or because they are creating shaded jars and remove the package data 
file. 

Because Log4j 2.x includes the annotation processor in the log4j-core jar most 
users have the packaging information present whether they realize it or not, so 
the upgrade to 3.x shouldn't impact too many people since they would have had 
to explicitly disable the annotation processor or remove the data file.

Furthermore, Log4j 3 will use the JDK ServiceLoader to locate the plugin 
information which is supported out of the box by the maven shade plugin. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to