Книга: Embedded Linux development using Eclipse
7.2.3 Naming Conventions
7.2.3 Naming Conventions
You’ve probably noticed by now that all of the Eclipse plug-ins have rather long names of the form org.eclipse.<feature>.<element of feature>_<number that looks like a version><maybe another big long number>.jar
. This is a naming convention that assures that all Java packages, or in this case Eclipse plug-ins, are unique. Eclipse requires that all plug-ins have a name that is unique throughout the world.
The name begins with a top-level Internet domain, such as .com, .org, .edu, etc., or one of the two-letter codes that identify a country outside the United States. The next element is a domain name representing the organization that wrote and/or maintains the package. Subsequent components of the name are specified by the organization and may include elements such as division, department, project, and so on.
For Eclipse the next component of the name is a component such as core
, ui
, or debug
, or a subproject such as cdt
, jtk
, or pde
. This is usually followed by the element of the component or subproject. Then comes the underscore followed by a version number. This is followed by another underscore, a “v”, and the date the package was built.
The convention further suggests that the Eclipse project name should match the plug-in name up to the first underscore.
- Driver Naming Conventions
- Conventions used in this document
- Conventions Used
- 12.8.9 Renaming Version-Controlled Files
- Conventions Used in This Book
- Site Naming
- Conventions used in this book
- Renaming network connections
- 4.5.2 Renaming Buffers
- 4.7.3 Renaming and Deleting Bookmarks
- 5.2.2 Deleting, Copying, and Renaming Files
- 6.7 Naming, Saving, and Executing Your Macros