[
https://issues.apache.org/jira/browse/HTTPCLIENT-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743185#comment-13743185
]
Morten Christensen commented on HTTPCLIENT-1388:
------------------------------------------------
Yes, I have seen them but it is highly troublesome to have alternative jars for
osgi because of 1) surprise that the normal jars won't work 2) Transitive
dependencies
Right now I am fighting with a maven project getting the right osgi jars
included and because of the many transitive dependencies of httpclient I
currently get some wrong dependencies included (trying to identifiy all
dependencies and including the osgi versions by hand).
It would be much easier for users and maintainers if there is just one jar for
both osgi and non-osgi use.
> HttpClient/Core lacks OSGI compatible fields in manifest
> --------------------------------------------------------
>
> Key: HTTPCLIENT-1388
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1388
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient
> Affects Versions: 4.2.5
> Environment: All environments
> Reporter: Morten Christensen
>
> To be usable in OSGI environments, HttpClient/HttpCore needs to have a osgi
> symbol name and import/export packages in the manifest file. An easy way to
> do this using maven is to use the maven-bundle-plugin
> (http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html)
> which will add the manifest attributes automatically. There is also a
> bndtools plugin to do this in ANT / eclipse.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
