Add generation of OSGi metadata and JPMS module-info #11
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.
As per our discussion in osgi/osgi#631 I am working on a more useful example of a containerized OSGi application. I want to setup a REST service application using Jakarta RS Whiteboard and put that in a container with checkpoint data.
While trying to create a
Resource
to handle the checkpoint/restore operations (see eclipse-osgi-technology/jakartarest-osgi@2ac4d8f) I noticed that org.crac does not contain OSGi metadata. It is therefore not possible to use it easily.The following PR adds the necessary build step to add OSGi metadata to the jar file. Additionally it also adds a JPMS module-info.class to the jar. Once this is merged and released I can move on with a PR for the Jakarta-RS Whiteboard, and then provide the example for CRaC`in an OSGi application.