Provide an API - Provide the functionality defined in an API.The semantic versioning white paper introduces two terms that are orthogonal to the imports and exports as well as implementing or delegating: For example:Įxport-Package: version=1.0.2 The import statement allows a version range to be set. In OSGi, the decision was taken to have a single export version. The ‘‘recommended’’ policy in OSGi is changing the part when there is: A version policy puts semantics on the version numbers. To survive versioning, one must have a ‘‘version policy’’. For internal development releases, bump the micro part of the bundle version. Every time when you release a bundle to the external world, bump the minor part of the bundle version.If you provide an API (as defined in te Semantic Versioning whitepaper) export the API package even if it is not in your project and put the provide:=true directive on the package export, e.g.bnd will then properly version this package when exported Changes that break providers (if any), increment minor. Any change that breaks consumers, increment major. Create a packageinfo file with “version 1.0” in each package directory and maintain it meticuously for each change to the package.
In contrast, versioning the packages and using Import-Package, bundles can be refactored and versioned independently. The result is that the system as a whole becomes brittle. The result is that systems can only evolve when everything is updated simultaneously. Aggregating dependencies increases the fan out of the transitive dependencies.
CRAZY BUMP 1.2 UPDATE
This requires an unnecessary update for a bundle that only depended on foo. For example, if a bundle contains two exported packages foo and bar and foo is not changed but bar has a major change, then the bundle version needs to also have a major change. Bundles are an ‘‘aggregate’’ and therefore must move as fast as the fastest moving exported packages they contain. The key concept to version in OSGi is the ‘‘package’’.
CRAZY BUMP 1.2 MANUAL
The goal of bnd is remove any manual work from versioning bundles as well as packages. bnd fully supports this model and provides many shortcuts. The OSGi has defined a versioning policy that is described in the Semantic Versioning whitepaper.
CRAZY BUMP 1.2 SOFTWARE
Where toys and prototypes can be developed ignoring evolution, real software requires a migration path to an unknown future. Versioning is probably the most painful part of developing real software.
0 kommentar(er)
