hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HTTPCLIENT-1019) httpclient-osgi Requires commons-logging 1.1.1 exported in OSGi, which they have no plan to move forward with
Date Wed, 27 Oct 2010 14:16:19 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925378#action_12925378
] 

Oleg Kalnichevski commented on HTTPCLIENT-1019:
-----------------------------------------------

> then there needs to be an apache release of commons logging that has been bundlefied
to export 1.1.1 of commons logging

What is the problem with using the one provided by Spring? I suspect Spring folks understand
thing or two about OSGi. This is basically what I did when testing the HttpClient OSGi bundle.


> http client needs to make commons logging optional in its osgi flavor

What do you mean by optional (and what should happen in case it is not available)? Can you
submit a patch against 4.0.x branch or trunk? 

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: New Feature
>          Components: HttpClient
>    Affects Versions: 4.0.1, 4.0.2, 4.0.3
>            Reporter: Zach Calvert
>             Fix For: Future
>
>
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message