OSGi compliant

[chuspb]

Hi,
Thanks for your project. We have built a wrapper of the library to be OSGi compliant. Do you want a PR in your project with this build?
Regards.

[veqryn]

Sure.
I'm not that familiar with OSGi, beyond some quick googling a minute ago, so a few questions:

1. Will we need to bump the version number?
2. Will we need to update the binaries in the maven repository?
3. Will this change how people include this library as a dependency? And if so, can people still include it the old/normal way?
4. Since this library doesn't actually have any dependencies (beyond 'test'), what does this do?
   thanks!,
   VEQ

[chuspb]

Hi,
I'm answering point by point;

1. That is up to you. If you update the version number (1.0.2 for example), then there is no doubt that this one is prepared to run in an OSGi environment.
2. Yes, that will be nice. That way we can download the new version without uncaching the previous library (1.0.1) .
3. There is no change. The library can be used in the same way. The only change is internal. Now, the jar is a bundle that can be deployed in any OSGi environment like Equinox, Apache Felix, Knopflerfish, ...
4. It doesn't includes any other dependency. It just creates a MANIFEST.MF file that is interpreted by the OSGi environments.

I will do a PR afterwards. You are free to change the version number, checking the created jar and so on. Please, do contact if any doubt.