[jira] [Commented] (LOG4J2-857) Add a new @PluginOrder annotation for ordering @Plugin classes

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537072#comment-17537072 ] 

ASF subversion and git services commented on LOG4J2-857:
--------------------------------------------------------

Commit 68025963868f1e17e7eab293112abfd67c5e2a67 in logging-log4j2's branch refs/heads/master from Matt Sicker
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=6802596386 ]

LOG4J2-857 - Support PluginOrder annotation and cleanups

- PluginManager is effectively renamed to PluginCategory with plugin collection logic moved to PluginRegistry
- PluginBundle replaces a map of category names to plugin type lists
- PluginOrder added for a generic plugin ordering annotation
- MergeStrategy updated to be injectable

Signed-off-by: Matt Sicker <ma...@apache.org>


> Add a new @PluginOrder annotation for ordering @Plugin classes
> --------------------------------------------------------------
>
>                 Key: LOG4J2-857
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-857
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Plugins
>            Reporter: Matt Sicker
>            Priority: Major
>
> Similar to how ConfigurationFactory plugins get precedence based on their order annotation, the same should be available for all plugins. This could be a more comprehensive solution for issues like LOG4J2-745.
> As the Order plugin is in log4j-core, a new annotation should be introduced in log4j-plugins for generic support.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)