[
https://issues.apache.org/jira/browse/LOG4J2-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854127#comment-16854127
]
Matt Sicker commented on LOG4J2-2621:
-------------------------------------
Ideally, the cache file format should be easily concatenated for use cases such
as jar shading/shadowing.
It may also be useful to use an abstraction over ClassLoader to allow for
plugins to be loaded from some sort of plugin module registry (doesn't
necessarily have to use the JPMS Module API, but that's one example; OSGi
bundles are another; WARs another).
> 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)
