Github user ta924 commented on the issue:
https://github.com/apache/logging-log4j2/pull/93
After some additional research I found that an internal library was
excluding all log4jplugins.dat files to ensure that only specific packages were
scanned. This was accomplished by a custom classloader. This forced the
PluginManager to to attempt resolution based off relocated package names from
the shade plugin. This modification made scanning and resolution possible for
the custom wrappers. I noticed that Spring Boot includes a log4jplugins.dat
file, which was getting loaded by default while trying to create a sample app.
That being said this becomes much more of a one off situation and doesn't fit
the normal operating patterns of log4j. I think the approach is a good fall
back in the event log4jplugins.dat file is not present and provided a
resolution mechanism for core plugins.
Again sorry for the late turn around on correspondence on the PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
