-
Notifications
You must be signed in to change notification settings - Fork 826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request: OSGI compatibility for the versioned kryo5 jar #811
Comments
@vikinghawk: I have no experience with OSGI and can't really validate any changes. Can you submit a PR that turns the versioned artifact into a valid OSGI bundle? It might suffice to add the |
Ya thats something we can do. I'll take that back to my team and we will work on getting that generated and tested. Thanks! |
Great! I'm planning to release Kryo 5.1.0 next week. If you can create a PR by then, I'll include it in the release. |
@vikinghawk and @theigl |
@Shradha-git: I merged your PR and applied some changes in 56817af to get rid of the bundle plugin warnings. Could you please test against the master or latest SNAPSHOT if you can still resolve the OSGI bundle using the current approach? |
Better test the current master. Travis doesn't seem to run at the moment and SNAPSHOTS haven't been published yet. |
@Shradha-git: Did you get a chance to verify against the current master? |
@theigl Verified osgi bundle against latest master code and bundle got resolved. MANITEST.MF got generated: |
@Shradha-git: Perfect, thank you! I'll release Kryo 5.1.0 in the coming days. |
@theigl What is the planned release date for Kryo 5.1.0 |
@Shradha-git: 5.1.0 has just been released and should be on Maven Central shortly. |
Looking at the Manfiest of the regular kryo-5.x dependency, it appears to be a valid OSGI bundle.
We would would like to use the versioned/shaded kryo5 dependency in our shared library, but we also need to support OSGI. Would it be possible to generate a valid OSGI manifest for the versioned jar as well?
The text was updated successfully, but these errors were encountered: