[
https://issues.apache.org/jira/browse/HTTPCLIENT-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739510#action_12739510
]
Richard Wallace 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>
That will set the version for org.apache.http and any subpackages that are
used. Alternatively, you can declare a dependency in maven on the bundle that
contains those packages and has an <Export-Package> manifest entry with the
proper versions and the bundle plugin will automatically find it and use those
versions.
Any chance you could do a minor release of the HttpCore OSGi bundle to get it's
manifest entries fixed?
> 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]
