Hello Ferry, On 31 Jul 2013, at 19:15 , Ferry Huberts <[email protected]> wrote:
> For (semantic) versioning in OSGi the bundle version actually is > meaningless. It's a marketing number, so 6.2.0 in your case. > > Only package versions have meaning. We've had this discussion in person before, but I don't agree and neither does the semantic versioning whitepaper [1] the OSGi alliance published. I quote: "The previous chapters use package imports and exports as examples. The reason is that the asymmetry between API consumers and providers is very clear with packages, especially with the OSGi service model where exported packages are always API. However, some analogies can be made with bundles and fragments. Requiring another bundle is similar to a short form of importing all the exported packages of that required bundle. The version of a bundle must therefore semantically aggregate the semantics of all its constituent packages. If any of these packages is incompatible with its providers then the bundle version must increment the minor version. If any of these packages is incompatible with consumers, the bundle version must increment the major version. It is clear, that on average, the version of a bundle will be much more volatile than the versions of its constituent packages, increasing the dependency problems." In other words, this whitepaper *does* attach specific semantics to bundle versions. Greetings, Marcel [1] http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
