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
Github user ta924 commented on the issue:
https://github.com/apache/logging-log4j2/pull/93
Sorry Gary had some things pop up on the work front that have eaten up most
of my time. I will get you an example as soon as things free up.
---
If your project is set up for it, you can
Github user ta924 commented on the issue:
https://github.com/apache/logging-log4j2/pull/93
Hi. Sorry for the delay had to prep for a few presentations the last couple
days. I will shoot to have one ready by the end of the week.
---
If your project is set up for it, you can reply to
Github user ta924 commented on the issue:
https://github.com/apache/logging-log4j2/pull/93
Submitted code change to introduce try-with-resources block, thank you for
the catch.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user ta924 commented on the issue:
https://github.com/apache/logging-log4j2/pull/93
I will evaluate the test logic in place to see if it is an option to create
a sample jar of the same structure.
---
If your project is set up for it, you can reply to this email and have your
Github user ta924 commented on a diff in the pull request:
https://github.com/apache/logging-log4j2/pull/93#discussion_r127734669
--- Diff:
log4j-core/src/main/java/org/apache/logging/log4j/core/config/plugins/util/ResolverUtil.java
---
@@ -329,6 +331,49 @@ private void
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
