🤔 What's the problem you're trying to solve?

I use this in an Eclipse plugin and currently need to repack the original cucumber jars into an OSGi bundle, but adding the info at the source has much benefits:

1. Additional metadata in the manifest is ignored by other tools
2. At build time there is the most rich information about used packages and versions so better metadata can be generated
3. Using the original jar ensures it can later be identified as such e.g. with a security scanner
4. No risk that different people repack the same jar under the same name with different settings
5. only do the work once than on each build / consumer

✨ What's your proposed solution?

Embed OSGi metadata into the manifest of the produced jar file at the first place using a lightweight approach that enhances the usual manifest with OSGi metadata.

⛏ Have you considered any alternatives or workarounds?

Currently the metadata is added after the fact but this has several drawbacks e.g. its easy to get out of sync and there is a risk of the same people doing slightly different things multiple time.

📚 Any additional context?

The preparation work for this was done here:

• Generate OSGi metadata cucumber-parent#61

This needs to be adapted in the following repositories to be fully effective but can be done iteratively, e.g we likely want to start at the root and after the release go on with the next:

• https://github.com/cucumber/messages/ --> java: Add OSGi metadata messages#344
• https://github.com/cucumber/gherkin/ --> Add OSGi metadata to the manifest gherkin#485
• https://github.com/cucumber/cucumber-expressions --> Add OSGi metadata cucumber-expressions#372
• https://github.com/cucumber/gherkin-utils/ --> Add OSGi metadata gherkin-utils#148
• https://github.com/cucumber/cucumber-jvm
• ...