Github user jpullmann commented on the pull request:
https://github.com/apache/jena/pull/134#issuecomment-206759395
Sorry for being absent yesterday (all-day meeting)! The answer regarding
OSGi given by @ajs6f is exhaustive. OSGi requires jars to explictily state
their code (packages) and service dependencies (components) to become
manageable by the framework. The former uses MANIFEST.MF headers. These were
missing in Dexx collection (plain jar):
`Manifest-Version: 1.0`
and I added them via creating a "Plug-in from Existing JAR Archives"
project in Eclipse:
```
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Dexx Collection
Bundle-SymbolicName: com.github.andrewoma.dexx.collection
Bundle-Version: 0.4.0
Bundle-Vendor: https://github.com/andrewoma/dexx
Export-Package: com.github.andrewoma.dexx.collection
```
Some "internal" packages are apparently not intended for sharing, I removed
them from the list of
exports now. As suggested I'll build and test the Dexx collection bundle..
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
