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

Latest revision as of 15:59, 18 May 2023

The EMO has moved this content to the Eclipse Project Handbook.

@@ Line 1: / Line 1: @@
-Eclipse projects must carefully manage their namespaces in order to help identify the producer of components and avoid namespace collisions.
+The EMO has moved this content to the [http://localhost/projects/handbook/#trademarks-code Eclipse Project Handbook].
-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. <code>org.eclipse.graphiti.core</code>, not <strike><code>org.eclipse.modeling.mdt.graphiti.core</code></strike> or <strike><code>org.eclipse.mdt.graphiti.core</code></strike>.
-=OSGi Bundle Names=
-OSGi Bundle names follow the same rules as [[#Java Package Names|Java Package Names]].