Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 332591

Summary:	separate internal name space from API
Product:	z_Archived	Reporter:	Steffen Pingel <steffen.pingel>
Component:	Mylyn	Assignee:	Kilian Matt <kilian.matt>
Status:	CLOSED MOVED	QA Contact:
Severity:	normal
Priority:	P3	CC:	kilian.matt
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Steffen Pingel

2010-12-14 18:41:43 EST

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.

Comment 1 Kilian Matt

2011-01-06 06:48:03 EST

Sound reasonable, I'll implement this in the TBR projects

Comment 2 Steffen Pingel

2011-01-07 17:35:24 EST

Can we at the same time tackle bug 332592  and bug 332593 as well?

Comment 3 Kilian Matt

2011-01-16 09:54:32 EST

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?

Comment 4 Steffen Pingel

2011-01-16 17:35:07 EST

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.

Comment 5 Steffen Pingel

2011-02-05 05:14:25 EST

Moving to TBR since is mostly done for the framework bundles.

Comment 6 Eclipse Webmaster

2022-11-15 11:45:08 EST

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