Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Development Resources/HOWTO/The Eclipse Code Namespace Policy
< Development Resources
Revision as of 17:04, 23 July 2013 by Wayne.eclipse.org (Talk | contribs) (New page: Eclipse projects must carefully manage their namespaces in order to help identify the producer of components and avoid namespace collisions. Exceptions to these rules must be approved by ...)
Eclipse projects must carefully manage their namespaces in order to help identify the producer of components and avoid namespace collisions.
Exceptions to these rules must be approved by the Project Management Committee and the EMO(ED).
Java Package Names
Java package names take the following form:
org.<forge>.<shortname>.<component>.*
Where:
- forge is the short name of the hosting forge, e.g. "eclipse", "locationtech", or "polarsys";
- shortname is the short name of the project (i.e. the last segment of the project id), e.g. "dali", "egit", "udig";
- component is project-specific
Java package names use the "flat" or "short" project name; they should not include, for example, the name of the top-level project or any parent/container project.
- e.g.
org.eclipse.graphiti.core, notorg.eclipse.modeling.mdt.graphiti.coreorg.eclipse.mdt.graphiti.core
OSGi Bundle Names
OSGi Bundle names follow the same rules as Java Package Names.