[
https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089887#comment-16089887
]
ASF GitHub Bot commented on LOG4J2-1852:
----------------------------------------
GitHub user ta924 opened a pull request:
https://github.com/apache/logging-log4j2/pull/93
modification to resolver to discover jar assests without the manipula…
…tion of asset paths.
This PR is to address issue
https://issues.apache.org/jira/browse/LOG4J2-1852. If the resource submitted
for scanning is of Jar protocol it utilizes a JarURLConnection to scan for
classes matching the test, it will no longer manipulate the URI for Jars. In
the event the protocol is file it will proceed with the existing approach.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ta924/logging-log4j2 PATCH-LOG4J2-1852
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/93.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #93
----
commit f7fdc3a3edae62f936233935968bfa0cdd0486e0
Author: Tanner Altares <[email protected]>
Date: 2017-07-17T14:01:04Z
modification to resolver to discover jar assests without the manipulation
of asset paths.
----
> 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)