[
https://issues.apache.org/jira/browse/LOG4J2-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647202#comment-13647202
]
Remko Popma commented on LOG4J2-230:
------------------------------------
Nick,
about 1)
I was also worried about NoClassDefFoundError.
Actually I kind of like having the variable there, makes it more
self-documenting.
2) I was thinking of a different solution but I realized that my idea would
only work during the maven build.
When the JUnit tests for either log4j-to-slf4j or for slf4j-impl are run in
isolation, it is not clear where to find the jar file for the other module...
Your solution solves that problem, thanks!
Not sure when I'll have the time (no, let's be honest, when I'll want to make
the time) to do this...
> Preempt StackOverflowEx when both slf4j-impl jar and log4j-to-slf4j jar are
> on the classpath
> --------------------------------------------------------------------------------------------
>
> Key: LOG4J2-230
> URL: https://issues.apache.org/jira/browse/LOG4J2-230
> Project: Log4j 2
> Issue Type: Improvement
> Components: SLF4J Bridge
> Affects Versions: 2.0-beta5
> Reporter: Remko Popma
>
> This ticket is to prevent issues like LOG4J2-204.
> Aiming for something similar to what is documented here:
> http://www.slf4j.org/codes.html#jclDelegationLoop
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
