Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Export-Package"
(4 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | The | + | The [[Eclipse]] top-level project uses the following convention for the Export-Package manifest attribute: |
− | * | + | * Newly added internal packages should not use x-internal exports unless there are very good reasons |
− | * | + | * For existing packages the x-internal export can be removed with PMC approval |
− | * | + | * Using x-friends is OK and should always be preferred over x-internals. The use of x-friends is an indication of tightly coupled bundles because its use is for when one bundle needs "approved" access to the internals of another bundle. |
− | + | [[Category:API]] | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + |
Revision as of 09:38, 15 January 2020
The Eclipse top-level project uses the following convention for the Export-Package manifest attribute:
- Newly added internal packages should not use x-internal exports unless there are very good reasons
- For existing packages the x-internal export can be removed with PMC approval
- Using x-friends is OK and should always be preferred over x-internals. The use of x-friends is an indication of tightly coupled bundles because its use is for when one bundle needs "approved" access to the internals of another bundle.