Plugin re-export anomalies

[pcdavid]

• 🆔 Bugzilla ID: #305286
• 📘 Project: Modeling / EMF Services / Transaction
• 🗓 Created: 2010-03-10T06:41:08Z
• ❓ Status: NEW /

[pcdavid]

Comment #0 on Wed Mar 10 2010 07:41:08 GMT+0100 (Central European Standard Time):

EMF appears to set a precedent that

org.eclipse.core.resources
org.eclipse.core.runtime

are not re-exported.

org.eclipse.emf.validation re-exports org.eclipse.core.resources

org.eclipse.emf.transaction re-exports org.eclipse.core.runtime

org.eclipse.emf.workspace.ui does not re-export org.eclipse.emf.workspace

Probably too late for M6. Perhaps these can be rationalized after Helios.

---

Comment #1 on Wed Mar 31 2010 23:06:43 GMT+0200 (Central European Summer Time):

Bundles are supposed to rexport their API dependencies.

For example, an API in org.eclipse.emf.validation requires the use of an API in org.eclipse.core.resources.

So we re-export org.eclipse.core.resources.

This way you only need to import org.eclipse.emf.validation and call org.eclipse.emf.validation API without having to add N other imports.

So the only issue here is that:

org.eclipse.emf.workspace.ui does not re-export org.eclipse.emf.workspace

Right?

---

Comment #2 on Thu Apr 01 2010 09:20:50 GMT+0200 (Central European Summer Time):

The missing org.eclipse.emf.workspace export is certainly the most obvious anomally.

The extra exports are subject to a policy that I do not understand. The indication that e4 will make org.eclipse.core.runtime/resources (I forget which) deprecated would perhaps suggest that projects should hide this dependency.

The exports of e.g. org.eclipse.emf.codegen.ecore are particularly hard to understand. 2 out of 3 EMFs. No Core. No JDT. No UI.

---

Comment #3 on Sat May 14 2022 15:51:23 GMT+0200 (Central European Summer Time):

Eclipse EMF Transaction is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/emf-transaction.

If this issue is relevant to you and still present in the latest release:

* Create a new issue at https://github.com/eclipse/emf-transaction/issues/.
  * Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  * In the GitHub description, start with a link to this bugzilla ticket
  * Optionally add new content to the description if it can helps towards resolution
* Update bugzilla ticket
  * Add to "See also" property (up right column) the link to the newly created GitHub issue
  * Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  * Set status as CLOSED MOVED

All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for EMF Transaction will be archived and made read-only.