[
https://issues.apache.org/jira/browse/LOG4J2-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854188#comment-16854188
]
Ralph Goers commented on LOG4J2-2621:
-------------------------------------
As I mentioned previously, as written the annotation processor is now
generating a Java source file. Anyone who can read Java can easily understand
it. If you are interested I would suggest checking out the branch and building
it. The build will fail in the log4j-osgi module as I haven't implemented OSGi
support yet. But you can find the plugin definitions for log4j-core in
target/generated-sources/annotations/org.apache.logging.log4j.core.plugins.Log4jPlugins.java.
The class is extremely simple as it creates an array of PluginEntry objects
and implements a getEntries() method to return the array.
> Create log4j-plugins module and use ServiceLoader to load plugins
> -----------------------------------------------------------------
>
> Key: LOG4J2-2621
> URL: https://issues.apache.org/jira/browse/LOG4J2-2621
> Project: Log4j 2
> Issue Type: Task
> Components: Plugins
> Affects Versions: 3.0.0
> Reporter: Ralph Goers
> Assignee: Ralph Goers
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
