You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2014/08/06 15:57:12 UTC

[jira] [Resolved] (LOG4J2-722) Commons Logging API classes missing from distribution

     [ https://issues.apache.org/jira/browse/LOG4J2-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remko Popma resolved LOG4J2-722.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.2

Changed documentation to mention that the Commons Logging jar is required in revisions 1616234 and 1616235.
Please verify and close.

> 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
>             Fix For: 2.0.2
>
>
> 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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org