[
https://issues.apache.org/jira/browse/LOG4J2-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854180#comment-16854180
]
Remko Popma commented on LOG4J2-2621:
-------------------------------------
If we are going to change the data file to a different format I would like to
propose changing it to a human-readable format rather than the current binary
format. That would allow users to inspect the data file in their jar and
potentially manually create/modify it if they have an issue with the annotation
processor.
I would favor XML because it is easy to parse and does not require external
dependencies to parse/serialize.
> 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)
