[
https://issues.apache.org/jira/browse/LOG4J2-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088126#comment-16088126
]
Gary Gregory commented on LOG4J2-1421:
--------------------------------------
Note that filters should be annotated with:
{code:java}
@Plugin(name = "<SomeFilterName>", category = Node.CATEGORY, elementType =
Filter.ELEMENT_TYPE, printObject = true|false)
{code}
You are missing:
{code:java}
elementType = Filter.ELEMENT_TYPE
{code}
Gary
> Custom plugins packaged in jar files are not loaded by "packages" property
> mecanism
> -----------------------------------------------------------------------------------
>
> Key: LOG4J2-1421
> URL: https://issues.apache.org/jira/browse/LOG4J2-1421
> Project: Log4j 2
> Issue Type: Bug
> Components: Plugins
> Affects Versions: 2.6
> Reporter: Anthony Maire
> Attachments: log4j-plugin-load-issue.zip
>
>
> the "packages" attribute in configuration file works properly to load custom
> plugins from Eclipse. However, if the plugin class is packaged alone in a jar
> file (without the Log4j2Plugins.dat file in it), the "packages" property load
> mecanism is not working.
> 2016-06-09 19:40:44,823 main DEBUG Took 0,001222 seconds to load 0 plugins
> from package test
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
