[
https://issues.apache.org/jira/browse/THRIFT-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147541#comment-13147541
]
Siamak Haschemi commented on THRIFT-184:
----------------------------------------
The list of imported and exported package will evolve over time. So you will
have to maintain these imports and exports for every single release!
The BND-tool automates this process:
1) You build your non-OSGi JAR (with missing OSGi headers)
2) You provide that JAR to BND. BND looks at any *.class within the JAR and
calculates the imported packages. The exported packages are your choice (its
the public API). But again BND can help you, because it supports wildcards.
3) BND produces an OSGi-compatible JAR
Note: Your distributed thrift-JAR will have no runtime-dependencies to BND or
OSGi. It is just enhanced with some metadata. I don't see why a build-time
depdency on BND is problematic.
> Add OSGi Manifest headers to the libthrift java library to be able to use
> Thrift in the OSGi runtime
> ----------------------------------------------------------------------------------------------------
>
> Key: THRIFT-184
> URL: https://issues.apache.org/jira/browse/THRIFT-184
> Project: Thrift
> Issue Type: New Feature
> Components: Java - Library
> Reporter: Siamak Haschemi
> Assignee: Jake Farrell
> Priority: Trivial
> Fix For: 0.8
>
> Attachments: bnd-0.0.249.jar, libthrift.bnd, osgi.patch
>
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> To be able to use Thrift in the OSGi runtime (see
> http://en.wikipedia.org/wiki/OSGi), some additional Manifest entries are
> needed. The bnd-tool (see http://www.aqute.biz/Code/Bnd) creates this entries
> automatically.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
