[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[eclipse.org-architecture-council] [Bug 292567] New: Practice of Exporting all packages
- From: bugzilla-daemon@xxxxxxxxxxx
- Date: Fri, 16 Oct 2009 14:58:26 -0400 (EDT)
- Auto-submitted: auto-generated
- Delivered-to: email@example.com
Product/Component: Community / Architecture Council
Summary: Practice of Exporting all packages
Classification: Eclipse Foundation
Component: Architecture Council
--- Comment #0 from Dave Carver <d_a_carver@xxxxxxxxx> 2009-10-16 14:51:42 EDT ---
There seems to be a standard practice amongst eclipse projects that they are
exporting all of their packages.
The eclipse project started out doing this, and as eclipse has growin to over
90 projects, most have followed what the eclipse project has done as a best
practice. Unfortunately, exporting internal packages can cause problems, and
in many ways does not encourage adopters to request API. It also doesn't
encourage projects to develop API themselves. Many projects consume across
plugins internals of other plugins.
There are some historical reasons why Eclipse did this during the transition to
osgi during 3.0, I suspect. Should the architecture council have a
recommendation on this practice?
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.