[
https://issues.apache.org/jira/browse/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925160#action_12925160
]
Zach Calvert commented on LOGGING-124:
--------------------------------------
The commons http client uses logging 1.1.1. Now there is no way for me to make
use of it on my OSGI stack. Here is the direct path that I'm now roadblocked
at. I add httpclient to my list of OSGI dependencies:
<dependency>
<groupId>org.apache.httpcomponents</groupId>
<artifactId>httpclient-osgi</artifactId>
<version>4.0.1</version>
</dependency>
I try to interact with httpcomponents on my equinox osgi stack and discover the
manifest to httpclient looks like:
Import-Package: javax.crypto,javax.crypto.spec,javax.net.ssl,javax.sec
urity.auth.x500,org.apache.commons.logging;version="1.1.1",org.apache
...
Since there is a direct dependency to 1.1.1 of commons logging, which no longer
supports OSGI, I'm now torn with either regressing to the old httpclient 3.0.1
or trying to wrap up the commons logging myself.
Yuck.
> Commons logging does not work in an osgi environment
> ----------------------------------------------------
>
> Key: LOGGING-124
> URL: https://issues.apache.org/jira/browse/LOGGING-124
> Project: Commons Logging
> Issue Type: Improvement
> Affects Versions: 1.1.1
> Reporter: Christian Schneider
>
> Commons logging should provide Manifest information for using it as an OSGI
> bundle. Eventually detection of logging engines and loading of configs should
> also be changed to make commons-logging osgi ready.
> I have given this problem the critical priority as currently many people are
> working on osgi projects and as many open source libs use commons-logging
> this is an important thing to solve.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
