-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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 Export-Package declarations for OSGi headers #6675
Conversation
This adds the necessary declarations to the Bnd plugin to export all non-internal packages for use in an OSGi environment. Affects: #6671
Codecov Report
@@ Coverage Diff @@
## 3.x #6675 +/- ##
============================================
+ Coverage 98.06% 98.07% +<.01%
+ Complexity 6189 6185 -4
============================================
Files 677 677
Lines 44682 44682
Branches 6169 6169
============================================
+ Hits 43819 43821 +2
+ Misses 314 309 -5
- Partials 549 552 +3
Continue to review full report at Codecov.
|
Thanks. Did you verify the jar file now contains the necessary entries? This looks odd to me though:
why would those two RxJava packages appear? |
Yep, the manifest now looks like this (from
In addition, I tried resolving a small test program and didn't run into any issues. If we see issues, I'll file new tickets.
It's considered a best practice in the current OSGi world to do this because it allows for better consistency in the presence of multiple bundles exporting the same packages. This blog post explains it a bit clumsily: https://blog.osgi.org/2007/04/importance-of-exporting-nd-importing.html It's not really critical to understand the details. It's probably enough to know that all of the various OSGi toolchains do this kind of "import my own exports" by default these days. I agree it looks odd. |
Thanks! |
This adds the necessary declarations to the Bnd plugin to export all
non-internal packages for use in an OSGi environment.
Affects: #6671