The doku. says:
"Usage
Using the Commons Logging Bridge is straightforward. 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."
Should I replace the commons.logging jar with jcl-bridge or should I just
add the jcl-bridge? I think it is not clearly defined in an OSGi-environment
which implementation is used if both JARs are installed. So, I would say
that the common.logging jar has to be replaced. This assumes that the
commons.logging api is somewhere exported. But the commons.logging api as
well as the commons.logging impl. are simple JARs but not bundles and they
can not be installed in an OSGi-environment. I would embed and export the
commons.logging api within the jcl-bridge.
...
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<configuration>
<instructions>
...
<Embed-Dependency>
commons-logging-api;version=1.1;scope=compile|runtime;inline=false
</Embed-Dependency>
<_exportcontents>
org.apache.commons.logging;version=1.1
</_exportcontents>
...
</instructions>
</configuration>
</plugin>
...
--
View this message in context:
http://apache-logging.6191.n7.nabble.com/Replace-commons-logging-with-jcl-bridge-tp39970.html
Sent from the Log4j - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
