[
https://issues.apache.org/jira/browse/HTTPCLIENT-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925361#action_12925361
]
Oleg Kalnichevski commented on HTTPCLIENT-1019:
-----------------------------------------------
Zach
While I agree the discovery mechanism of Commons Logging is utterly broken for
containers and managed environments with complex class loader hierarchies, I
personally do not think there is anything wrong with the Commons Logging API.
We had a fair share of Logging Wars on the dev and user lists in the past and
would not like them to repeat.
There is _nothing_ that prevents you from using a compatibility layer such as
jcl-over-slf4j provided by slf4j and whatever concrete implementation you find
to be OSGi friendly.
I will happily tweak the bundle manifest but It is unlikely we will be able to
replace Commons Logging with a different logging toolkit in the stable (4.x)
branch. We can revisit the issue for HttpClient 5.0 (if that is of any
consolation to you).
Oleg
> 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.1, 4.0.2, 4.0.3
> 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]
