[
https://issues.apache.org/jira/browse/LOG4J2-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma reassigned LOG4J2-722:
----------------------------------
Assignee: Remko Popma
> Commons Logging API classes missing from distribution
> -----------------------------------------------------
>
> Key: LOG4J2-722
> URL: https://issues.apache.org/jira/browse/LOG4J2-722
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Holger Stenzhorn
> Assignee: Remko Popma
>
> The page [Commons Logging
> Bridge|http://logging.apache.org/log4j/2.x/log4j-jcl/index.html] mentions
> under *Usage* that...
> bq. Simply add the bridge jar along with the other Log4j 2 jars and all
> logging done using the Commons Logging API will be routed to Log4j.
> ...and under *Requirements* only that...
> bq. The Commons Logging Bridge requires at least Java 6 and is dependent on
> the Log4j 2 API.
> But this is actually not the case since the API classes from the package
> {{org.apache.commons.logging}} are not bundled within the bridge JAR.
> So currently the name {{log4j-jcl-2.0.jar}} is a misnomer and so the solution
> would be to either...
> * rename {{log4j-jcl-2.0.jar}} to {{log4j-jcl-impl-2.0.jar}} (following the
> example of {{log4j-slf4j-impl-2.0.jar}}) and distribute the
> {{commons-logging-api-1.x.jar}} along with the Log4J2 distribution (perhaps
> as log4j-jcl-api-2.0.jar)
> * package the necessary Commons Logging API classes directly into the
> {{log4j-jcl-2.0.jar}}
> The second solution is how SLF4J handles things, how the description page
> above describes things and how the SLF4J binding/bridge is supposed to work
> (see LOG4J2-723)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
