Community
Participate
Working Groups
The general convention for Eclipse bundles is to use an "internal" segment in the package name to denote packages that are not API, i.e. are not intended to be accessed by clients and are exported as x-internal in the Manifest. The Reviews project should follow this convention.
Sound reasonable, I'll implement this in the TBR projects
Can we at the same time tackle bug 332592 and bug 332593 as well?
It is implemented for TBR core plugin, the internal package is still visible to the ui until I've a nice API for that. Is it ok, if i put everything in the ui plugins in the internal namespace?
Great! Absolutely fine with me. We usually treat connector core and UI as one component, i.e. make the UI a friend of core and don't export any public API. Since the UI is inherently tightly coupled to the corresponding core I wouldn't necessarily bother with API at all.
Moving to TBR since is mostly done for the framework bundles.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn