Like other open source projects, the code base for the Eclipse project should avoid using names that reference a particular company or their commercial products. | Naming Conventions From Eclipsepedia Contents 1 General o Eclipse Workspace Projects o Java Packages o API Packages o Internal Implementation Packages o Test Suite Packages o Examples Packages o Additional rules 2 Classes and Interfaces 3 Methods 4 Variables 5 Constants 6 Plug-ins and Extension Points 7 System Files and Settings General Like other open source projects the code base for the Eclipse project should avoid using names that reference a particular company or their commercial products. Eclipse Workspace Projects When Eclipse is being used to develop plug-ins for the Eclipse project the name of the Eclipse workspace project should match the name of the plug-in. For example plug-in is developed in an Eclipse workspace project named . Java Packages The Eclipse Platform consists of a collection of Java packages. The package namespace is managed in conformance with Sun s package naming guidelines subpackages should not be created without prior approval from the owner of the package subtree. The packages for the open-source Eclipse project are all subpackages . The first package name segment after is generally the subproject name followed by the component name. . subproject . component . - General form of package names The following subprojects are assigned at the time of writing . component . - Java development tooling . component . - Plug-in development environment The following package name segments are reserved internal - indicates an internal implementation package that contains no API tests - indicates a non-API package that contains only test suites examples - indicates a non-API package that contains only examples These name are used as qualifiers and appear between the subproject and component name . subproject .internal. component . - internal package . subproject .tests. component . - tests
