[
https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089643#comment-16089643
]
Tanner Altares commented on LOG4J2-1852:
----------------------------------------
I can work on submitting a patch this week. [~garydgregory] the
Log4j2Plugins.dat file was included in the executable Jar and was discovered by
ResolverUtil, unfortunately when discovery happens the URI is rewritten. On
initial discovery it is found under <PARENT JAR Path>!/BOOT-INF/lib/<JAR
CONTAINING Log4j2Plugins.dat>, then modified to <PARENT JAR PATH>. To by pass
this you can generate a flattened uber jar with the shade plugin, but tolerance
to handle Spring Boot's packaging seems like an easier approach will utilizing
the framework.
> 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)
