Jump to: navigation, search

Difference between revisions of "Development Resources/HOWTO/The Eclipse Code Namespace Policy"

Line 31: Line 31:
  
 
TBD
 
TBD
 +
 +
<hr/>
 +
''This page is moderated by the EMO.''

Revision as of 22:27, 23 July 2013

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 standard reverse DNS 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"; and
  • component is project-specific

Multiple component segments are permitted.

Examples:

  • org.eclipse.emf.core, org.eclipse.emf.edit, org.eclipse.emf.edit.ui; and
  • org.locationtech.udig.resources

Java package names use the "flat" or "short" project name in the third segment; 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.

Java Archive (JAR/WAR/EAR) Names

TBD

JavaScript

TBD


This page is moderated by the EMO.