[
https://issues.apache.org/jira/browse/LOG4J2-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holger Stenzhorn updated LOG4J2-723:
------------------------------------
Description:
The page [Log4j 2 SLF4J
Binding|http://logging.apache.org/log4j/2.x/log4j-slf4j-impl/index.html]
mentions under *Usage* that...
bq. Simply include the Log4j 2 SLF4J Binding jar along with the Log4j 2 jars to
cause all SLF4J logging to be handled by Log4j 2.
...and under *Requirements* only that...
bq. The Log4j 2 SLF4J Binding requires at least Java 6 and has a dependency on
the Log4j 2 API.
But this is actually not the case since the API classes from the package
{{org.slf4j.*}} are not bundled within the binding JAR.
The solutions could either be to...
* distribute the {{slf4j-api-1.x.x.jar}} along with the Log4J2 distribution
(perhaps as {{log4j-slf4j-api-2.0.jar}})
* package the necessary SLF4J API classes directly into the
{{log4j-slf4j-impl-2.0.jar}}) (renaming that one then simply to
{{log4j-slf4j-2.0.jar}})
The second solution is how SLF4J handles things, how the description page above
describes things and how the Commons Logging binding/bridge is supposed to work
(i.e. {{log4j-jcl-2.0.jar}}) (see LOG4J2-722)
was:
The page [Log4j 2 SLF4J
Binding|http://logging.apache.org/log4j/2.x/log4j-slf4j-impl/index.html]
mentions under *Usage* that...
bq. Simply include the Log4j 2 SLF4J Binding jar along with the Log4j 2 jars to
cause all SLF4J logging to be handled by Log4j 2.
...and under *Requirements* only that...
bq. The Log4j 2 SLF4J Binding requires at least Java 6 and has a dependency on
the Log4j 2 API.
But this is actually not the case since the API classes from the package
{{org.slf4j.*}} are not bundled within the binding JAR.
The solutions could either be to...
* distribute the {{slf4j-api-1.x.x.jar}} along with the Log4J2 distribution
(perhaps as {{log4j-slf4j-api-2.0.jar}})
* package the necessary SLF4J API classes directly into the
{{log4j-slf4j-impl-2.0.jar}}) (renaming that one then simply to
{{log4j-slf4j-2.0.jar}})
The second solution is how SLF4J handles things, how the description page
aboves describes things and how the Commons Logging binding/bridge is supposed
to work (i.e. {{log4j-jcl-2.0.jar}}) (see LOG4J2-722)
> SLF4J API classes missing from distribution
> -------------------------------------------
>
> Key: LOG4J2-723
> URL: https://issues.apache.org/jira/browse/LOG4J2-723
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Holger Stenzhorn
>
> The page [Log4j 2 SLF4J
> Binding|http://logging.apache.org/log4j/2.x/log4j-slf4j-impl/index.html]
> mentions under *Usage* that...
> bq. Simply include the Log4j 2 SLF4J Binding jar along with the Log4j 2 jars
> to cause all SLF4J logging to be handled by Log4j 2.
> ...and under *Requirements* only that...
> bq. The Log4j 2 SLF4J Binding requires at least Java 6 and has a dependency
> on the Log4j 2 API.
> But this is actually not the case since the API classes from the package
> {{org.slf4j.*}} are not bundled within the binding JAR.
> The solutions could either be to...
> * distribute the {{slf4j-api-1.x.x.jar}} along with the Log4J2 distribution
> (perhaps as {{log4j-slf4j-api-2.0.jar}})
> * package the necessary SLF4J API classes directly into the
> {{log4j-slf4j-impl-2.0.jar}}) (renaming that one then simply to
> {{log4j-slf4j-2.0.jar}})
> The second solution is how SLF4J handles things, how the description page
> above describes things and how the Commons Logging binding/bridge is supposed
> to work (i.e. {{log4j-jcl-2.0.jar}}) (see LOG4J2-722)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
