Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update packaging to generate OSGI manifest data, to better support deployment in OSGI environments.
Sorry - take #2 on this pull request, there was a missing commit.
The first commit is simple enough, it just uses the maven-bundle-plugin to add the OSGI headers to the manifest of each jar file.
The second commit is more of a breaking change. OSGI does not like multiple bundles (jar files) providing classes from the same package namespace. In this case, you're using the same namespace for the odata-client-msgraph and odata-client-msgraph-client-builder packages (com.github.davidmoten.msgraph). I've moved the builder classes into their own namespace, but this might have implications for client code if people have used any of the builder classes directly.