Jump to: navigation, search

Development Resources/HOWTO/The Eclipse Code Namespace Policy

< Development Resources
Revision as of 16:04, 23 July 2013 by Wayne.eclipse.org (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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, not org.eclipse.modeling.mdt.graphiti.core or org.eclipse.mdt.graphiti.core.

OSGi Bundle Names

OSGi Bundle names follow the same rules as Java Package Names.