[
https://issues.apache.org/jira/browse/HTTPCLIENT-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739532#action_12739532
]
Oleg Kalnichevski commented on HTTPCLIENT-865:
----------------------------------------------
> There are 2 ways to get around having to define versions on each imported
> package. Since they are all
> in the same sub package you can just use
>
> <Import-Package>org.apache.http.*;version="4.0",*</Import-Package>
I thought about it but unfortunately HttpCore and HttpCore share the same
'org.apache.http' namespace.
> Any chance you could do a minor release of the HttpCore OSGi bundle to get
> it's manifest entries fixed?
Usually ASF releases tend to escalate into a very painful and time consuming
affair for me, often leading to outbursts of domestic violence in my family. I
often end up sleeping on a sofa in the living room severely beaten by my wife.
I would hate having to do a release just because of OSGi bundle. This can be
fixed with the next planned release of core (4.1), though
Oleg
> HttpClient OSGi Export-Package doesn't specify version
> ------------------------------------------------------
>
> Key: HTTPCLIENT-865
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-865
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.0 Beta 2
> Reporter: Richard Wallace
> Fix For: 4.0 Final
>
>
> The "Export-Package" manifest entry doesn't specify the version of the
> package being exported. This means that packages importing it can't specify
> a version to import.
--
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]
