httpclient-osgi Requires commons-logging 1.1.1 exported in OSGi, which they
have no plan to move forward with
-------------------------------------------------------------------------------------------------------------
Key: HTTPCLIENT-1019
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1019
Project: HttpComponents HttpClient
Issue Type: Bug
Affects Versions: 4.0.3, 4.0.2, 4.0.1
Reporter: Zach Calvert
Priority: Critical
If you are trying to run the httpclient-osgi version 4.0.1, there is little
opportunity to make it work without hand rolling your own apache commons
logging. Using the Maven descriptor:
<dependency>
<groupId>org.apache.httpcomponents</groupId>
<artifactId>httpclient-osgi</artifactId>
<version>4.0.1</version>
</dependency>
You will find that the downloaded bundle manifest has:
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
...
Emphasis on org.apache.commons.logging;version="1.1.1". Basing my
understanding of the bug at
https://issues.apache.org/jira/browse/LOGGING-124
which I have also commented on, there is no such thing as an exported osgi
package version 1.1.1 of commons logging due to problems with the OSGi
classloader.
Support needs to be made to make commons logging optional in the osgi world and
if the logging mechanism for commons logging isn't there, then move forward to
something that doesn't make waves for the OSGi runtime.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
