This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 197517 - Identify public packages and correct package names
Summary: Identify public packages and correct package names
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Cosmos (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Joel Hawkins CLA
QA Contact:
URL:
Whiteboard: wsdm
Keywords:
Depends on:
Blocks: 196050
  Show dependency tree
 
Reported: 2007-07-23 14:02 EDT by Hubert Leung CLA
Modified: 2012-01-03 13:54 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hubert Leung CLA 2007-07-23 14:02:34 EDT 
- make sure public packages only include public interfaces and implementations (i.e. don't include internal interfaces or classes in public packages) 
- mark internal packages with "internal" in the package name (need to confirm if it is necessary)
- Hide interfaces and implementations that are not used directly when writing extension code into private packages.  (e.g. the ServiceRegistry interface)  Internal interfaces or classes that are in public packages need to be moved to an internal package.  
- We should have a review of the public APIs since they will become a contract between COSMOS and consuming products, and we will need to maintain the compatibility of these APIs in future releases.
Comment 1 Ruth Lee CLA 2008-08-06 11:00:31 EDT 
Moving all open bugzillas that are targeted to iterations in the past to the next iteration (i13).
Comment 2 David Whiteman CLA 2008-08-13 10:49:26 EDT 
since this references code that is currently archived, will mark this as wontfix just to get it off the books for things to do.   if the code is resurrected, we can reopen this.