You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2023/12/02 00:14:00 UTC

[jira] [Resolved] (LOG4J2-858) Improve PluginManager to filter plugins by class

     [ https://issues.apache.org/jira/browse/LOG4J2-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker resolved LOG4J2-858.
--------------------------------
    Fix Version/s: 3.0.0
                       (was: 2.3)
         Assignee: Matt Sicker
       Resolution: Fixed

This was addressed as part of LOG4J2-2803.

> Improve PluginManager to filter plugins by class
> ------------------------------------------------
>
>                 Key: LOG4J2-858
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-858
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Plugins
>            Reporter: Matt Sicker
>            Assignee: Matt Sicker
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> If I could construct, for instance, {{new PluginManager<Appender>()}} instead of the usual way via category, then I could group plugins within the same category or separate categories more easily along with providing better type safety. This would reduce a lot of the "unchecked" warning suppression, plus it would make things a bit neater.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)