You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2019/06/15 21:07:00 UTC
[jira] [Resolved] (LOG4J2-2621) Create log4j-plugins module and use
ServiceLoader to load plugins
[ https://issues.apache.org/jira/browse/LOG4J2-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-2621.
---------------------------------
Resolution: Fixed
Changes merged
> 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)