[ https://issues.apache.org/jira/browse/LOG4J2-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743919#comment-13743919 ]
Gary Gregory commented on LOG4J2-363: ------------------------------------- Well, it depends on your POV I suppose. If you develop code that logs to Apache Commons Logging (ACL) then you will include the (misnamed IMO, it should be log4j-acl) log4j-jcl artifact ID to your POM, which includes the dependency above to ACL. Then your app can happily log to one of the ACL supported target log libs. If the dep is on the ACL API jar, then your application will not log unless you add the 'normal' dependency in your POM. In both cases, you'll need to add a dep to the target log lib(s). If your unit tests never uses a code path that causes logging to an ACL target lib, then you can get away with depending on the ACL API jar. The other case is if your app depends on an ACL back-end that is NOT implemented in commons-logging, then you'd want the API and the impl would be superflous. That seems like the exception rather than the norm. What am I missing? > change dependency from commons logging impl to commons logging API > ------------------------------------------------------------------ > > Key: LOG4J2-363 > URL: https://issues.apache.org/jira/browse/LOG4J2-363 > Project: Log4j 2 > Issue Type: Dependency upgrade > Components: JCL Bridge > Affects Versions: 2.0-beta9 > Reporter: Roland Weiglhofer > Fix For: 2.0-beta9, 2.0 > > > The JCL Bridge should depend on the common logging API but not on commons > logging impl. > <dependency> > <groupId>commons-logging</groupId> > <artifactId>commons-logging-api</artifactId> > <version>1.1</version> > </dependency> -- 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org