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

ASF GitHub Bot commented on HTTPCLIENT-1673:
--------------------------------------------

GitHub user bimargulies opened a pull request:

    https://github.com/apache/httpclient/pull/34

    HTTPCLIENT-1673: revert change, which was not necessary

    and add test that proves that it's not necessary.
    Mostly provide bones of future OSGi tests.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bimargulies/httpclient 
httpclient-1673-osgi-exports

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/httpclient/pull/34.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #34
    
----
commit 8031af51d90d179a0978032f20db716d6128b080
Author: Benson Margulies <[email protected]>
Date:   2015-08-12T17:39:00Z

    HTTPCLIENT-1673: revert change, which was not necessary
    and add test that proves that it's not necessary.
    Mostly provide bones of future OSGi tests.

----


> org.apache.http.entity.mime.content is missing from exports of OSGi bundle
> --------------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1673
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1673
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>    Affects Versions: 4.5
>            Reporter: Benson Margulies
>             Fix For: 4.5.1
>
>
> I can't get to org.apache.http.entity.mime.content.ContentBody in OSGi 
> because that package is missing from the export list in the MANIFEST.MF.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to