| [orbit-dev] Import-Package in osgi.bnd |
|
I’m working on a new recipe to address
https://bugs.eclipse.org/bugs/show_bug.cgi?id=558284. I used ebr to create the recipe and am working on reviewing osgi.bnd, specifically Import-Package. In previous threads, IIRC, Roland Grunberg had advised me to pay special attention to Import-Package and Carston Reckord had suggested some ways to assemble the list of imports. I used a regex search to find all of the import statements in all the java files, then trimmed from the last ‘.’ to the end of the line to get the package list (and sorted to get unique list, etc). I was wondering about packages vs. subpackages because in some of the existing osgi.bnd files there seems to be a mix of toplevelpackage.* and toplevelpackage.subpackage.* in the Import-Package section. I went to look at the bndtools doc (https://bnd.bndtools.org/heads/import_package.html) and it says “The default for this header is *, resulting
in importing all referred packages. This header therefore rarely has to be specified.” This is actually what ebr:create-recipe provides: Import-Package: \ * Can I get a refresher on what we need to have in Import-Package with regard to package vs. subpackage and why ‘*’ isn’t sufficient? Thanks! Tony Homer |