Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.0.0
-
None
-
None
Description
As part of splitting log4j 2 into smaller components it is clear that the plugin system, and especially the annotation processor, could be split into a separate module. Also, to be more compliant with the Java module system it might be beneficial to generate a Class file with all the plugin information instead of the data file currently being generated.
Moving the plugins to a separate module is going to impact anyone who has created a Log4j 2 plugin as the package for the plugin annotations must change.
Attachments
Issue Links
- is related to
-
LOG4J2-673 plugin preloading fails in shaded jar files
- Open
- relates to
-
LOG4J2-954 log4j-slf4j-impl 2.1 leads to errors
- Open
-
LOG4J2-369 How to include the log4j2 lib jar into a jar with my application class and run it ?
- Resolved
-
LOG4J2-1852 Plugins lookup by package is not compatible with Spring Boot jar packaging
- Resolved
-
LOG4J2-2604 Generate reflect-config.json for GraalVM during annotation processing
- Open