OSGi import/export headers

[rotty3000]

• <developers><developer><id> element added to silence a complaint from bnd about well formed entries
• let bnd generate default manifest spec entries, as well as setting all other headers
• added BND SPI annotations to add the necessary parts to make ServiceLoader work in OSGi (passively)

fixes #242

Signed-off-by: Raymond Augé raymond.auge@liferay.com

Make sure that:

• [ I would but it's missing ] You have read the contribution guidelines.
• You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
• You use the code formatters provided here and have them applied to your changes. Don't submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.

Issue description

New Public APIs

Additional context

[rotty3000]

A future step would be to add verification step that assures the metadata does in fact work in an OSGi framework. I can contribute this later.

[rotty3000]

This contribution now fully verifies OSGi metadata continuously with the build. If the metadata breaks, the build will fail.

[rotty3000]

@ascertrobw could you confirm if this works for you?

[mp911de]

Thanks a lot. The SPI pom now defines two additional dependencies that will come transitives and we have to use annotations on the service loader component. That is quite a high price for supporting a technology with perceived little demand.

[ascertrobw]

@ascertrobw could you confirm if this works for you?

Yep, good our side Raymond.

[rotty3000]

@mp911de it's not the first time I hear this argument. Let me see what I can do to mitigate that cost, give me a few days.