Skip to content
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

Add package versions to OSGi metadata #982

Merged
merged 2 commits into from
Jul 5, 2018

Conversation

io7m
Copy link
Contributor

@io7m io7m commented Jul 1, 2018

This adds version declarations to each exported package in the
OSGi metadata. This allows users to specify that they want a
specific version (or range of versions) of JNA in their OSGi
applications/libraries.

Fix #975

This adds version declarations to each exported package in the
OSGi metadata. This allows users to specify that they want a
specific version (or range of versions) of JNA in their OSGi
applications/libraries.

Fix java-native-access#975
@io7m
Copy link
Contributor Author

io7m commented Jul 1, 2018

I haven't touched the platform jar as there's something in there I'm not sure about: It uses Require-Bundle which is considered very bad practice in modern OSGi. I'd have to know if there was some specific reason this is being used before I go modifying the manifest.

@matthiasblaesing
Copy link
Member

Thank you Mark, in general this would be ok to merge. Please also add an entry to CHANGES.md. Please see the other entries as a template.
In regard to the Require-Bundle problem - JNA and JNA platform are build together and released together so in this case you don't gain much by switching from bundle to package dependencies. For external users it might be worth adding the version to the exported packages of the platform, as the platform might be split in the future.

This adds package versions to the platform jar in case the bundle is broken up
into separate pieces in the future. In addition, add an entry to CHANGES.md.

Fix java-native-access#975
@io7m
Copy link
Contributor Author

io7m commented Jul 5, 2018

I've added the versions to the platform jar, and added an entry to CHANGES.md.

@io7m
Copy link
Contributor Author

io7m commented Jul 5, 2018

Not... sure what that build failure is about. I don't think it's related to the changes I made.

@matthiasblaesing
Copy link
Member

Looks good - thank you for taking care of it.

@matthiasblaesing matthiasblaesing merged commit 31846f3 into java-native-access:master Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants