Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
The Braintree component has its own JUL-SLF4J bridge class BraintreeLogHandler.
If there's an existing log framework on the classpath that can already do such bridging (E.g JBoss Logging on WildFly and Quarkus), then you end with an endless recursion situation when Braintree invokes any of its logger methods.
It'd be nice to have the option of disabling BraintreeLogHandler in such scenarios.
Attachments
Issue Links
- links to