Hello, I understand all the disadvantages of using require-bundle over import-package, but I'm not sure what's the effect of using the bundle version as exported package version, at least by default (i.e. when need it, we can create the "packageinfo" file manually to control the package version by hand). I am having a hard time enforcing the usage of packageinfo files in my team. I created a packageinfo file for every exported package but whenever we create new packages we forget to create the file or, what's worse, when modifying code we forget to bump the package version; so we might end up with problems where a bundle with a bugfix ends up exporting a package with the same version as the buggy package so the fix might or might not work in some systems. Would it be acceptable to, by default, version packages with the bundle version? This is what the maven-bundle-plugin does when there's no packageinfo anyway. Also, the bundle version is much more visible since we use maven and the maven-release-plugin, which bumps the bundle version itself so we are sure two released bundles will never have the same version therefore neither would the packages.
This sounds better than using Require-bundle since we can still for example refactor a bundle without redeploying the consumers. But is it still ok? One drawback I see is complexifying (i.e. slowing down) wiring/start-up due to the (unnecessary) number of exporters of packages that might actually contain the same code. We are using the maven-bundle-plugin. For now bndtools is not an option. Ultimately what I think is the best solution is to start using the baselining feature of bnd, but until then, is versioning all packages in a bundle with the bundle-version problematic?? Thanks for any insight, Alejandro DISCLAIMER: Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
