[
https://issues.apache.org/jira/browse/LOG4J2-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088182#comment-16088182
]
Gary Gregory commented on LOG4J2-1421:
--------------------------------------
Hi All,
But that does not solve the initial problem of course. For this to work, we
need to scan the whole classpath for packages and plugins within those.
Would you be willing to provide a PR on GitHub?
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)
