[
https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090939#comment-16090939
]
Tanner Altares commented on LOG4J2-1852:
----------------------------------------
I wanted to come back here and clarify a comment that I previously made around
the Log4j2Plugins.dat being present in the package. I was incorrect the
Log4j2Plugins.dat wasn't being excluded due to the fact that the jar was being
shaded and relocating the paths. The implementation used is creating a custom
configuration and adding packages directly view addPackages on the
PluginManager. When ran with Spring Boot's packaging the PluginManager isn't
able to discover from the collectPlugins method. For this situation it is more
of an isolated case, but the PR should suffice for normal operations along with
this scenario. I will add additional tests to the PR and submit for review.
> Plugins lookup by package is not compatible with Spring Boot jar packaging
> --------------------------------------------------------------------------
>
> Key: LOG4J2-1852
> URL: https://issues.apache.org/jira/browse/LOG4J2-1852
> Project: Log4j 2
> Issue Type: Bug
> Components: Plugins
> Affects Versions: 2.7
> Environment: Spring Boot 1.5.x, java 8
> Reporter: Maksym Novoseltsev
> Priority: Minor
>
> Here is you can find a description of the issue and pretty usefull answer
> from Spring Boot team regarding the very same issue:
> https://github.com/spring-projects/spring-boot/issues/8637
> Also you will find a sample project there that will help to reproduce issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
