Jump to: navigation, search

Difference between revisions of "OSGi API Guidelines"

Line 8: Line 8:
 
* Fragment dependencies - A bundle fragment inherits the Require-Bundle and Import-Package statements from its host.  A fragment should not re-specify requires or imports that are already specified by the host, because a change in imports on the host can cause a fragment to fail to resolve.  A fragment may specify additional requirements that are not specified by its host as needed.
 
* Fragment dependencies - A bundle fragment inherits the Require-Bundle and Import-Package statements from its host.  A fragment should not re-specify requires or imports that are already specified by the host, because a change in imports on the host can cause a fragment to fail to resolve.  A fragment may specify additional requirements that are not specified by its host as needed.
  
 +
[[Category:API]]
 
[[Category:Equinox]]
 
[[Category:Equinox]]
 
----
 
Back to [[API Central]]
 

Revision as of 10:28, 1 December 2006

This page is currently a place holder for a more formal guideline document. Information here is currently in the form of rough notes and should not be construed as definitive guidelines.

The OSGi MANIFEST.MF and Equinox plugin.xml files form part of the API contract of a bundle. These metadata files define what a bundle exposes to other bundles, and what it consumes from other bundles. Care must be taken when modifying this metadata, because in many cases it can have an impact on downstream bundles.

Topics:

  • When should required bundles be re-exported?
  • The effect of adding/removing dependencies on downstream bundles
  • Fragment dependencies - A bundle fragment inherits the Require-Bundle and Import-Package statements from its host. A fragment should not re-specify requires or imports that are already specified by the host, because a change in imports on the host can cause a fragment to fail to resolve. A fragment may specify additional requirements that are not specified by its host as needed.